MySQL Governor limits recommendation

Issue

Often the limits for LVE and DB Governor are set incorrectly while it's an important step to lower server load and restrict users.

Solution

According to the recommendations, this is the most suitable template for setting the Governor limits:

current=LVE_CPUSPEED*2.5
short=LVE_CPUSPEED*1.5
middle=LVE_CPUSPEED*1.1
long=LVE_CPUSPEED*0.9

If you face spike CPU consumption with these limits, it is recommended to reduce the excess of the current and short limits:

current=LVE_CPUSPEED*1.5
short=LVE_CPUSPEED*1.1

If the average level of CPU consumption is too high, then it is recommended to reduce the middle and long limits:

middle=LVE_CPUSPEED*0.8
long=LVE_CPUSPEED*0.5

Notes: 

1. Please note that these recommendations on setting limits for MySQL Governor are general. The exact values of the limits for the effective work of MySQL and the site as a whole depend on many factors.
2. The same clues are applicable to the IO limits – thecurrentandshortIO limits for MySQL Governor can exceed IO LVE limits, but themiddleandlongcannot.

Cause

Inconsistent Governor limits caused DB spikes and performance degradation.

Useful links

https://docs.cloudlinux.com/cloudlinux_os_components/#mysql-governor-limits