Sizing Avantra
Sizing Avanta components is important to ensuring system stability as your landscape grows and product usage increased. The recommendations listed are the minimum sizing requirements. Where possible, it's recommended to implement Avantra in an environment that can adapt to the landscape over time.
Avantra Server sizing
We suggest the following when sizing the hardware for your Avantra Server.
The storage requirements in the table below have two options:
- The Avantra Server and database reside on separate hosts
- The Avantra Server and database reside on the same host
Server Sizing
| # of SAP Systems & Instances | CPU | Memory | Storage (without DB) | Storage (with DB) |
|---|---|---|---|---|
| < 300 | dual-core 2 GHz | 8 GB | 50 GB | 50 GB |
| 301 - 1000 | quad-core 3 GHz | 16 GB | 50 GB | 100 GB |
| 1001 - 3000 | quad-core 3 GHz | 24 GB | 100 GB | 150 GB |
| 3000+ | quad-core 3 GHz | 32 GB | 100 GB | 200 GB |
Avantra Database Sizing
For an Avantra database (where the database is stand alone to the Avantra server), we recommend the following minimum sizing be adopted:
Standalone Database Sizing
| # of SAP Systems & Instances | CPU | Memory | Storage |
|---|---|---|---|
| < 300 | dual-core 2 GHz | 8 GB | 50 GB+ |
| 301 - 1000 | quad-core 3 GHz | 16 GB | 100 GB+ |
| 1001 - 3000 | quad-core 3 GHz | 24 GB | 150 GB+ |
| 3000+ | quad-core 3 GHz | 32 GB | 200 GB+ |
Avantra Agent sizing
Standard usage
The Avantra agent is designed to be a light-weight application that runs on monitored systems using between 1 and 2 GB of memory.
The exception to this recommendation would be:
- If the agent is performing a high number of custom checks or automations that are memory intensive.
- If the agent is monitoring a large number of remote systems e.g. SAP Systems and/or databases in remote mode. If this is- the case, use the Remote monitoring sizing below as a reference.
If the agent is acting as a Gateway agent through which other agents communicate to contact the Avantra server. If this is the case, use the Gateway Agent sizing below as a reference.
Remote monitoring
When operating in an environment where you will be performing remote monitoring (e.g. a RISE with SAP or HEC environment) where you will be using a single agent to monitor multiple remote systems, then the following sizing guidelines should be reviewed.
We suggest the following when sizing the hardware as well as the associated JVM memory allocation in the file /[avantra-directory]/agent/cfg/jvm.options.
Remote Monitoring Agent Sizing
| SAP Systems handled | CPU | Memory | Disk | JVM Setting |
|---|---|---|---|---|
| up to 10 | dual-core 2 GHz | 8 GB | 50 GB+ | -Xmx4096m |
| 10 - 20 | quad-core 3 GHz | 16 GB | 100 GB+ | -Xmx8192m |
| 20 - 30 | quad-core 3 GHz | 24 GB | 150 GB+ | -Xmx16384m |
Gateway agent
The Avantra agent can also be configured as a gateway through which other agents can communicate with an Avantra server. This is particularly useful for multi-network scenarios or NAT routing or other complex network setups.
We suggest the following when sizing the hardware for an Avantra Gateway Agent as well as the associated JVM memory allocation in the file /[avantra-directory]/agent/cfg/jvm.options.
Gateway Agent Sizing
| SAP Systems handled | CPU | Memory | Disk | JVM Setting |
|---|---|---|---|---|
| up to 300 | dual-core 2 GHz | 8 GB | 50 GB+ | default |
| 301 - 1000 | quad-core 3 GHz | 16 GB | 100 GB+ | -Xmx4096m |
| 1001 - 3000 | quad-core 3 GHz | 24 GB | 150 GB+ | -Xmx8192m |
| 3000+ | quad-core 3 GHz | 32 GB | 200 GB+ | -Xmx16384m |
Advanced sizing
For more information about Avantra sizing and for advanced setup guidance, refer to the Avantra knowledge base article Sizing & performance tuning considerations.