Skip to content

MySQL Governor

Keep MySQL/MariaDB fair on multi-tenant servers with live monitoring and intelligent throttling.

Database fairness

Visibility and control for shared databases

Governor reads active threads, maps them through the Simuzo dbmap, evaluates the user’s limits, and applies throttling when needed. Admins get a monitoring UI plus CLI tools for status and maps.

  • Live thread monitoring
  • User and database mapping (dbmap)
  • Throttle markers in the UI
  • systemd service with journal logs
  • Optional plugin packaging for supported MySQL/MariaDB versions
MySQL Governor admin interface
Workflow

How operators use Governor

Enable

Turn on MySQL Governor in Settings and ensure the service is running.

Map

Rebuild dbmap so MySQL users and databases resolve to system accounts.

Monitor

Watch live threads, throttling state, and pair with cGroup package design.

FAQ

Common questions

What does MySQL Governor require?

MySQL or MariaDB with performance_schema available, a rebuilt database map mapping MySQL users/databases to system users, and the governor service enabled.

What happens when a user is throttled?

When usage exceeds the user’s database resource plan, long-running queries may be terminated and pressure is reduced until usage returns within limits.

Can I rebuild mappings after adding databases?

Yes. Rebuild the database map from the admin UI or CLI when users or databases change so attribution stays accurate.

Ready to secure your hosting nodes?

Install Simuzo on your panel server, enable isolation and limits, and give users a safer multi-tenant environment.

Product news, security improvements, and release notes for hosting providers.