Sizing and scalability considerations


This topic provides information about performance, scalability and reliability test results for PATROL for Docker 1.1.00.

The following tables provide information about the tested configuration scenarios. It also provides information on the PATROL Agent performance and the application performance with respect to CPU utilization and memory in Windows platforms.


Related topics

Planning

Installing

Tested configuration scenario for Docker Swarm Cluster

Platform

Number 
of containers

Number of 
instances monitored

Number of 
parameters monitored

Microsoft Windows Server 2012 R2 x64
2 vCPU, 4 GB RAM

1000

5263

12543


Performance Metrics Summary

Microsoft Windows Server 2012 R2 x64

Metrics

PATROL Agent performance

Java

 

Average

Maximum

Average

Maximum

CPU (in %)

0.825

10.5

0.928

28.56

Memory (MB)
(Working Set)

58

60

297

325

Note

The tests have been performed with the following values of the specified configuration variables.

PATROL configuration variable

Value

/AgentSetup/AgentTuning/runqSchedPolicy

2

If the number of containers in monitored swarm cluster is more than 1000, consider tuning the following variables.

PATROL configuration variable

Value

/DKR/HOST/<swarm manager host name>/maxHeapSize

256 MB

Default value = 512 MB

/DKR/HOST/<swarm manager host name>/javaOpts

-DthreadPool.SwarmPerformance=15 -DthreadPool.SwarmInventory=15

Default value = 50.

 

Impact on the Docker host

During the tests, a minimal impact was observed on the Docker daemon process. Typically, for every collection cycle, CPU utilization of the daemon process increases by 7 to 10% and the memory utilization increases by 50 to 60 MB.

Tested configuration scenario for Docker host

Platform

 

Number 
of containers

Number of 
instances monitored

Number of 
parameters monitored

Microsoft Windows Server 2012 R2 x64
4 vCPU, 4 GB RAM

500

2090

5224


Performance Metrics Summary

Microsoft Windows Server 2012 R2 x64

Metrics

PATROL Agent performance

Java

 

Average

Maximum

Average

Maximum

CPU (in %)

0.543

8.545

0.904

33.33

Memory (MB)
(Working Set)

36.44

36.63

287

367

 

Note

Set the PATROL configuration variable, /AgentSetup/AgentTuning/runqSchedPolicy to 2.

Impact on the Docker host

During the tests, a minimal impact was observed on the Docker daemon process. Typically, for every collection cycle, CPU utilization of the daemon process increases by 3 to 5% and the memory utilization increases by 40 to 50 MB.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*