Skip to content

Server Configuration Optimizer

The AI Config Advisor analyzes your MySQL configuration and server metrics to recommend optimal settings. Available on paid plans only.

How it works

The optimizer analyzes: - Current MySQL variables (buffer pool, query cache, connections, etc.) - Server resource usage (RAM, CPU patterns) - Query performance patterns and workload - MySQL version and InnoDB settings

It then provides AI-powered recommendations tailored to your specific workload and hardware.

Run an analysis

  1. Open the MySQL Optimizer page (from server card or nav menu)
  2. Go to the Overview tab
  3. Find the AI Config Advisor section
  4. Click Request AI Recommendations

Rate limiting: To prevent excessive AI usage, you can request recommendations once per cooldown period (configurable per server).

Review recommendations

When analysis completes, you'll see: - Recommended changes with before/after values - Reasoning explaining why each change helps - Expected impact on performance - Risk level for each change

Config change tracking

All MySQL configuration changes are automatically tracked: - Change history tab shows all past modifications - Chart annotations display when config changes occurred - Before/after health scores help measure impact - Rollback information for reversing changes if needed

View the Config Changes tab to see: - Timestamp of each change - Variables modified - Old vs new values - Who/what triggered the change

Apply recommendations

Important: Configuration changes are typically applied manually. The UI provides: - Exact commands to run on your server - SQL statements for MySQL variable changes - File edit instructions for my.cnf changes

Always: - Backup config files before making changes - Test in staging if possible - Apply incrementally and monitor impact - Restart MySQL when required for changes to take effect

Best practices

  • Apply one recommendation at a time to isolate impact
  • Monitor health scores and query performance after each change
  • Keep the config change history for troubleshooting
  • Re-run analysis after major workload changes or version upgrades
  • Use the 24-hour health charts to validate improvements