This topic provides information about performance and scalability test results for PATROL for Amazon EC2 2.1.00.01.
Amazon EC2 KM can successfully monitor approximately 70 K CloudWatch metrics for a given AWS account using one PATROL Agent.
The following tables list the configuration that was used for running the performance and scalability tests.
Microsoft Windows Server 2012 R2 Datacenter
PATROL for Amazon EC2 2.1.00.01
|PATROL Agent 11.0.00 + Patch 02||JRE 1.8.0_121||TrueSight Presentation Server 11.0.00|
|Max Heap Size||Min Heap Size||Ec2 Thread Pool||JMX remote||javaOpts|
|3072m||256m||100, 100||Enabled||-Xms256m -Xmx3072m -DEC2ThreadPool.ThreadCount=100,100|
Monitored environment details
We have monitored one Amazon Web Service account with the services as listed below:
Count (per AWS region)
Total per region
Total Services in Account
Performance, Scalability, and Reliability
Total PATROL Instances
Total PATROL Parameters
PATROL Agent – Private Bytes
Java process – Private Bytes
Performance data of PATROL Agent and Java collector
Average CPU in %
(Value is not normalized)
|Average working set|
|Java Collector||53.68||3.38 GB|
|PATROL Agent||5.03||137.8 MB|
|Average Heap Utilization||Max Heap Utilization||Peak Thread Count||Thread Count||Daemon Thread Count|
|2 GB||2.63 GB||146||135||22|
Recommendations for monitoring the services in a large environment
- Use filters to exclude AWS regions that do not have any services to be monitored.
- Tune in the number of Java threads as per the javaOpts variable documented in the Configuration table.