Scalability

This topic provides information about performance and scalability test results for PATROL for Amazon Web Services 2.1.00.02. 

Amazon Web Services 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. 

Service configuration

Platform

Processors

Memory

Microsoft Windows Server 2012 R2 Datacenter

4

8 GB

Setup details

KM

PATROL Agent

JRE

TrueSight console

PATROL for Amazon Web Services 2.1.00.02

PATROL Agent 11.0.00 + Patch 02

JRE 1.8.0_121

Truesight Presentation Server 11.0.00

Configuration 

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:

 AWS Services

Count (per AWS region)


us-east-1

us-east-2

us-west-2

EC2

1000

1000

1000

EBS

1000

1000

1000

Lambda

200

200

200

DynamoDB

200

200

200

Total per region

2400

2400

2400

Total Services in Account

7200

Performance, Scalability, and Reliability

Scalability

Total PATROL Instances

Total PATROL Parameters

PATROL Agent – Private Bytes

Java process – Private Bytes

19.2 K

70 K

160 MB

3.47 GB

Resource Utilization

Performance data of PATROL Agent and Java collector

Process

Average CPU in %

(Value is not normalized)

Average working set

Java Collector

68.86

3.435 GB

PATROL Agent

6.76

170 MB

JVM resources

Average Heap Utilization

Max Heap Utilization

Peak Thread Count

Thread Count 

Daemon Thread Count

2.2 GB

2.76 GB

184

170

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.