Configuration

The MySQL Configuration page lets you edit low-level my.cnf settings for your database service, without needing terminal access.

How to Change Configuration​

1. Open OpenPanel and navigate to MySQL > Configuration.
2. Modify the values you want to change.
3. Click Save Changes to apply changes.

Settings are written to your account's custom.cnf file, and the MySQL/MariaDB container is restarted to apply them.

Optimize Database​

When the Configuration page opens, OpenPanel checks your database service in the background and suggests settings that fit how it's actually used. While it checks you'll see Checking your database for possible optimizations....

If it finds something to improve, an Optimize Database banner shows at the top of the page and an optimize icon (⚡) shows next to each setting that has a suggestion.

1. Click the optimize icon next to a setting, or Review all in the banner.
2. The Confirm Changes dialog shows the previous value, the new value and why it's suggested for each setting.
3. Click Save Changes to apply them and restart the service, or Cancel to close the dialog without changing anything.

The banner also shows what the suggestions are based on: the server version, the memory limit and current memory use of the database service, the number of databases, how much InnoDB and MyISAM data you have, and the uptime.

Suggestions are based on:

• Memory limit of your MySQL/MariaDB service, and whether it was ever stopped for running out of memory. Used for the InnoDB buffer pool, temporary tables, Performance Schema and how many connections fit in memory.
• Your data: how much data and indexes your InnoDB and MyISAM tables use. For example the key buffer is lowered when you have no MyISAM tables, and the buffer pool is raised when your InnoDB data doesn't fit in it.
• Usage counters since the service started: disk reads, temporary tables written to disk, refused connections, new threads, log buffer waits and sort merges. These are only used after the service has been running for at least an hour.
• Current connections: many idle connections suggest a lower wait_timeout.
• Error log: recent Too many connections, max_allowed_packet and redo log size errors.

Only settings that are listed on the page and supported by your server version are suggested, so the suggestions work for both MySQL and MariaDB. For example innodb_log_file_size is not suggested on newer MySQL versions that size the redo log with innodb_redo_log_capacity.

Available Options​

The list of configurable keys is determined by the system administrator. By default, the following are available:

• max_allowed_packet
• max_connect_errors
• max_connections
• open_files_limit
• performance_schema
• sql_mode
• thread_cache_size
• interactive_timeout
• wait_timeout
• log_output
• log_error
• log_error_verbosity
• general_log
• general_log_file
• long_query_time
• slow_query_log
• slow_query_log_file
• join_buffer_size
• key_buffer_size
• read_buffer_size
• read_rnd_buffer_size
• sort_buffer_size
• innodb_log_buffer_size
• innodb_log_file_size
• innodb_sort_buffer_size
• innodb_buffer_pool_chunk_size
• innodb_buffer_pool_instances
• innodb_buffer_pool_size
• max_heap_table_size
• tmp_table_size

Customizing Available Options

Administrators can change which keys are exposed here by editing /etc/openpanel/mysql/keys.txt (one key per line). If that file doesn't exist, the default list above is used.