Sizing Avantra

Sizing your Avantra components correctly is very important to ensure system stability as your landscape grows and your use of the product increases. The recommendations listed here are considered the minimum sizing requirements and where possible, we recommend implementing Avantra in an environment that can be adapted to the landscape over time i.e. easily add or remove resources as required.

Avantra Server Sizing

We suggest the following when sizing the hardware for your Avantra Server.

Please note 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 2GHz	8GB	50GB	50GB
301 - 1000	quad-core 3GHz	16GB	50GB	100GB
1001 - 3000	quad-core 3GHz	24GB	100GB	150GB
3000+	quad-core 3GHz	32GB	100GB	200GB

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:

Stand-alone Database Sizing
# of SAP Systems & Instances	CPU	Memory	Storage
< 300	dual-core 2GHz	8GB	50GB+
301 - 1000	quad-core 3GHz	16GB	100GB+
1001 - 3000	quad-core 3GHz	24GB	150GB+
3000+	quad-core 3GHz	32GB	200GB+

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, please 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, please 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 2GHz	8GB	50GB+	-Xmx4096m
10 - 20	quad-core 3GHz	16GB	100GB+	-Xmx8192m
20 - 30	quad-core 3GHz	24GB	150GB+	-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 2GHz	8GB	50GB+	default
301 - 1000	quad-core 3GHz	16GB	100GB+	-Xmx4096m
1001 - 3000	quad-core 3GHz	24GB	150GB+	-Xmx8192m
3000+	quad-core 3GHz	32GB	200GB+	-Xmx16384m

Advanced Sizing

For more information about Avantra sizing and for advanced setup guidance, please refer to this solution article on the topic.