System Resources Affected by IP SLA
IP SLA affects the following system resources:
- Memory—The memory consumed by IP SLA is approximately 8 Megabytes. The 30,000 statistical data entries consume a little over 7 Megabytes while the eight IP SLA entries consume less than 1 Megabyte.
- CPU—Through its use of the Tracked Object Manager, IP SLA may have a significant effect on CPU utilization. The number of probe sessions and frequency of ICMP echo requests sent on behalf of these sessions affect the CPU. The functioning of IP SLA and its scheduler does not have a large effect on the CPU, with the exception of displaying a large amount of data collected for an IP SLA entry.
- Storage and persistence—The information pertaining to the configuration is persistent and it is stored in nonvolatile storage. The timing statistics are stored in RAM and IP SLA DOES NOT distribute this data to the other line cards.
- Network bandwidth—If you configure path monitoring, IP SLA uses the traceroute program to determine the path to the destination host. Indirectly, IP SLA creates probe sessions with the Tracked Object Manager, which uses the network bandwidth to perform its tasks.