CloudLinux MySQL Governor explained: database limits on shared hosting

On shared servers, all websites use the same MySQL server. One slow query running over and over can make every site on the server sluggish. MySQL Governor, part of CloudLinux, tracks database usage per cPanel account and slows down accounts that use far more than their share, keeping the database fast for everyone.

Before you start

MySQL Governor runs on MdmHost servers automatically. To investigate your own database usage you need cPanel access and, ideally, phpMyAdmin or a WordPress query monitor plugin.

How it works

• Every query is attributed to the cPanel account whose database user ran it.
• Governor measures CPU time and disk reads and writes per account over short and longer periods.
• When an account goes over its database limits, it is restricted: its queries continue but run within the account's CloudLinux LVE limits, so they are slower.
• When usage drops, the restriction is lifted automatically.

How it relates to your other limits

Database work counts against the same CPU and I/O limits you see in Resource Usage. A site with heavy queries can show CPU or I/O faults even when page traffic is low. Long queries also keep PHP processes waiting, which raises entry processes and can cause 508 errors.

Signs your account is restricted

• The site is slow mainly on pages with searches, filters or reports.
• The admin area is slow when loading lists of orders, posts or users.
• Resource Usage shows CPU or I/O at the limit without a traffic spike.

Find heavy queries

• WordPress: install the Query Monitor plugin temporarily and look at slow or duplicate queries per page.
• phpMyAdmin: check table sizes (see phpMyAdmin); huge wp_options, wp_postmeta or log tables are common culprits.
• Support: MdmHost can confirm whether your account was restricted and which database user was involved; open a ticket.

Fixes that work

1. Cache pages with LiteSpeed Cache so most visits do not hit the database at all (see LiteSpeed Cache).
2. Clean bloated tables: expired transients, post revisions, spam comments and old logs from security or statistics plugins.
3. Reduce autoloaded options in wp_options; removed plugins often leave large autoloaded rows.
4. Add indexes to custom tables used in WHERE clauses.
5. Replace heavy plugins, such as related-posts or statistics plugins that run expensive queries on every page.

For resellers

MySQL Governor settings are server-wide and managed by MdmHost. If one of your customers is restricted often, help them optimise or move them to a package with higher CloudLinux limits (see limits for resellers).

Frequently asked questions

Does MySQL Governor block my site?

No. It slows an account that uses too much database time, rather than stopping it. Pages still load, just more slowly, until usage drops.

Are database sizes limited by Governor?

No. Database size counts toward your disk quota. Governor is about CPU and I/O usage.

Can I see Governor statistics myself?

The detailed statistics are server-side. Resource Usage in cPanel shows the CPU and I/O effects; support can share specifics.