Bug ID 642926: Increased MySQL Memory usage when APM is provisioned on lower-end systems.

Last Modified: Nov 22, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:

Fixed In:
13.1.0, 13.0.0 HF1

Opened: Feb 02, 2017
Severity: 3-Major


You may notice mysql process continuously consuming high amount of CPU and memory resources when APM is provisioned. This can be seen in the results of 'top' command where mysql will be continuously listed. The issue applies to BIG-IP with 32 GB or less system memory available.


You may notice general performance issues on BIG-IP systems with system memory 32 GB or lower when MySQL usage is high.


When APM module is provisioned, if either of the following is true: * logging configuration uses on-box publisher and log-level setting leads to high amount of logging data (e.g., DEBUG). * LocalDB or OAuth Authorization server is configured with a DB instance and traffic is being processed.


1) Remove following 2 lines from file '/var/lib/mysql/cnf/apm.cnf' -- innodb_buffer_pool_size = 1G sort_buffer_size = 256M and save file before exiting. 2) Restart MySQL service using -- 'bigstart restart mysql'

Fix Information

MySQL configuration when APM is provisioned now works as expected on lower-memory BIG-IP systems.

Behavior Change