Scalability

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. 

Service configuration

Platform

Processors

Memory

Microsoft Windows Server 2012 R2 Datacenter

48 GB

Setup details

KM

PATROL Agent

JRE

TrueSight console

PATROL for Amazon EC2 2.1.00.01

PATROL Agent 11.0.00 + Patch 02JRE 1.8.0_121TrueSight Presentation Server 11.0.00

Configuration 

Max Heap SizeMin Heap SizeEc2 Thread PoolJMX remotejavaOpts
3072m256m100, 100Enabled-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

Total per region

2000

2000

2000

Total Services in Account

6000

Performance, Scalability, and Reliability

Scalability 

Total PATROL Instances

Total PATROL Parameters

PATROL Agent – Private Bytes

Java process Private Bytes

18 K

60 K

130 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 Collector53.683.38 GB
PATROL Agent5.03137.8 MB

JVM resources

Average Heap UtilizationMax Heap UtilizationPeak Thread CountThread Count Daemon Thread Count
2 GB2.63 GB14613522


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. 


Was this page helpful? Yes No Submitting... Thank you

Comments