Bug ID 703171: High CPU usage for apmd, localdbmgr and oauth processes

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:

Fixed In:

Opened: Jan 23, 2018

Severity: 3-Major


High CPU Usage for apmd, localdbmgr, and oauthd with large configurations.


Depending on the operation: + The process on the second device exhibits high CPU usage + The loading device exhibits high CPU usage. APM end user traffic might not be processed by APM until it is done processing all the config changes. The amount of time service is down depends on how large the configuration is.


-- APM provisioned. -- BIG-IP has a large configuration (i.e., a large number of virtual servers). -- One of the following: + A full config sync happens from one device (with a large configuration) to another device. + When loading BIG-IP configurations that contain a large number of virtual servers.



Fix Information

Startup processing of apmd, localdbmgr, and oauthd have been optimized to reduce the CPU usage.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips