Scalability and best practices for ICMP- Ping
This section describes some best practices that you can use while configuring PATROL for Light Weight Protocols for pinging a device using ICMP. Device configuration becomes critical when a single resource agent is configured to ping many devices.
Hardware recommendation
The following table lists the hardware recommendations for the tested configuration scenarios in Windows Server 2016 and Red Hat Enterprise Linux 6.0 x86_64 platforms:
Platform | Configuration Item | Value |
|---|---|---|
| Windows Server 2016 | CPU | 2.2 GHz |
RAM | 4 GB | |
Type | 64 bit | |
Red Hat Enterprise Linux 6.0 x86_64 | CPU | 2.4 GHz |
RAM | 4 GB | |
Type | 64 bit |
Scalability and sizing best practices
Consider the following requirements to set up devices to ping according to the optimization to achieve best performance:
# | Number of devices | Poll interval (sec) | Timeout (ms) | Number of retries | Transmit packet size (bytes) | Dynamic IP address support1 |
|---|---|---|---|---|---|---|
1 | 1-500 | 10-300 and above | 1000 | 1-10 | 32-1024 | Yes |
2 | 500-1000 | 30-300 and above | 1000 | 1-5 | 32-1024 | Yes |
3 | 1000-1500 | 60-300 and above | 1000 | 1-5 | 32 | Yes |
4 | 1500-2500 | 120-300 and above | 1000 | 1-4 | 32 | Yes |
5 | 2500-3500 | 180-300 and above | 1000 | 1-2 | 32 | Yes |
6 | 3500 and above | 300 | 1000 | 1-2 | 32 | Yes |
Configuration best practices
The following tables provide information about the tested configuration scenarios. It also provides the information on the PATROL Agent performance and the application performance with respect to CPU utilization, memory and threads in Red Hat Enterprise Linux 6.0 x86_64 platforms.
Tested configuration scenarios in the Windows Server 2016 platform:
# | Number of devices | Poll interval (sec) | Timeout(ms) | Number of retries | Transmit packet size (bytes) | Dynamic IP address support1 | PATROL Agent Performance | PPM application performance | Threads | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Average CPU utilization (%) | Maximum CPU utilization (%) | Memory (MB) | Average CPU utilization (%) | Maximum CPU utilization (%) | Memory (MB) | ||||||||
1 | 500 | 10 | 1000 | 10 | 1024 | Yes | 1.5 | 15 | 40 | 5 | 36 | 10 | 204 |
2 | 1000 | 30 | 1000 | 5 | 1024 | Yes | 1.5 | 32 | 31 | 9.5 | 56 | 17 | 404 |
3 | 1500 | 60 | 1000 | 5 | 32 | Yes | 1 | 18.7 | 42 | 1.1 | 20 | 22 | 604 |
4 | 2500 | 120 | 1000 | 4 | 32 | Yes | 1.37 | 32 | 43 | 12 | 75 | 27 | 1004 |
5 | 3500 and above | 180 | 1000 | 2 | 32 | Yes | 1.3 | 20 | 67 | 3.8 | 55 | 45 | 1292 |
Tested configurarion scenarios Red Hat Enterprise Linux 6.0 x86_64 platform:
# | Number of devices | Poll interval (sec) | Timeout(ms) | Number of retries | Transmit packet size (bytes) | Dynamic IP address support1 | PATROL Agent Performance | PPM application performance | Threads | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Average CPU utilization (%) | Maximum CPU utilization (%) | Memory (MB) | Average CPU utilization (%) | Maximum CPU utilization | Memory (MB) | ||||||||
1 | 500 | 10 | 1000 | 10 | 1024 | Yes | 1.4 | 4.1 | 32 | 1.3 | 3.1 | 8 | 200 |
2 | 1000 | 30 | 1000 | 5 | 1024 | Yes | 2.4 | 7.5 | 45 | 13 | 18 | 10 | 400 |
3 | 1500 | 60 | 1000 | 5 | 32 | Yes | 2.6 | 9.2 | 55 | 9.3 | 17 | 11 | 512 |
4 | 2500 | 120 | 1000 | 4 | 32 | Yes | 2.4 | 8 | 72 | 12 | 18 | 12.5 | 512 |
5 | 3500 and above | 180 | 1000 | 2 | 32 | Yes | 2.8 | 10.1 | 73 | 13 | 18 | 13 | 512 |
1-You can also configure devices with static IP address.