Database Auto-Configuration

Our platform, Smart Auto-Configuration, does the heavy lifting by fine-tuning MySQL, MariaDB, and Percona databases to match the resources assigned to each container. Specifically, it tweaks settings in the /etc/my.cnf configuration file, focusing on:

• key_buffer_size
• table_open_cache
• myisam_sort_buffer_size
• Innodb_buffer_pool_size

Beginning from the 5.7 and 8.0 editions of MySQL/Percona and MariaDB 10.x, the platform introduces two extra settings:

1. innodb_buffer_pool_instances (Deprecated in MariaDB 10.6.x, with a single pool instance)
2. innodb_buffer_pool_chunk_size

If you’re looking to tweak any settings listed above by hand, just make sure to adjust the JELASTIC_AUTOCONFIG environment variable to either “false,” “disable,” or “0.” Otherwise, any custom tweaks you make will get replaced.

Note: You have the option to change any settings in the /etc/my.cnf file, even those that are managed by the platform’s Smart Auto-Configuration, by specifying them in the /etc/mysql/conf.d/custom.cnf file instead.

Legacy Implementation

To tweak the settings on those old containers by hand, you will need to remove the line that starts with “#Jelastic autoconfiguration mark.” from the beginning of the /etc/my.cnf file.