A server featuring a single Xeon quad core CPU can be used to handle a continuous load of up to 500 HTTP requests per second at about 120 megabit per second. A peak load of up to 1000 HTTP requests per second at 250 megabit per second is possible but may result in a slightly increased latency of HTTP responses. Additional CPUs can be installed to increase the throughput capacity of the server.
Values for orientation: 1000 active (concurrently working) users cause approx. 50 HTTP requests per second and occupy approx. 40 TCP connections.
We recommend installing at least 4GB of RAM per configured nevisProxy instance.
The table below shows you possible values for four different requirement examples:
|Connections||Sessions (using the internal session cache)||Typical memory consumption||Sample server configuration|
|250||2000||1 to 2 GB||1x 4 cores Xeon processor with 4GB memory|
|400||8000||3 to 4 GB||1x 4 cores Xeon processor with 8GB memory|
|1000||15000||5.5 to 7 GB||1x 8 cores Xeon processor with 16GB memory|
|2000||30000||10 to 12 GB||2x 8 cores Xeon processor with 32GB memory|
Typical memory consumption is the memory allocated when starting the process. The memory consumption usually increases during operation.
Memory consumption depends on your configuration, the number of concurrent clients and the number of supported sessions. During operation memory consumption increases (an increase of one gigabyte or more is not uncommon).The table above shows example values for a nevisProxy instance hosting a single service.
Also consider the recommendations on the sizing requirements in the nevisProxy reference guide (chapters "Scaling" and "Memory Limitation").
Authenticating users involves usually nevisProxy, nevisLogRend, nevisAuth, nevisIDM, and the database. As a rule of thumb, you should allocate one CPU core to serve 10 authentication transactions (user login) per second.
Java-based NEVIS products or components
We recommend installing at least 1GB of RAM for each Java-based instance (such as nevisAuth, nevisIDM, nevisLogRend). The memory (heap) is limited by the section of
-Xmx parameter within the
vmargs.conf configuration file of the corresponding instance.
Memory consumption highly depends on your configuration.
Also consider the recommendations on the sizing requirements in the reference guide of the corresponding NEVIS product or component.
Disk and disk space
Every instance writes log files to the local disk. See the nevisAdmin reference guide, chapter "Log Settings", on how to define the size and the generation of log files to be kept on the file system.
We recommend keeping at least 1 GB of log data per instance on the disk.
For the database appliance we recommend using high performing SSDs for storage and a minimum amount of at least 60 GB disk space.