Only a well-seasoned DBA admin can make cheese out of. MySQL Tuner is a nice tool, but it will give you indications (not rock-solid recommendations) that will change from day to day. and when are you killing your server with overloads and overusage of resources?!? Nevertheless, when having a quick look at your modifications to the MySQL config, I can only ask myself and you : what (the he*&) typ of databases are you running. I agree with W - this is not the place for DBA optimization. NOTE: skip-name-resolve=1 produces a database error in our backup logs, which is why it is disabled. Innodb_buffer_pool_size (>= 3.3G) if possible. Table_definition_cache (2400) > 3113 or -1 (autosizing if supported) Join_buffer_size (> 256.0K, or always use indexes with JOINs) Reduce your SELECT DISTINCT queries which have no LIMIT clause When making adjustments, make tmp_table_size/max_heap_table_size equal (specially the conclusions at the bottom of the page). We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found. I'd like some guidance about what to change/add/remove form my.cnf based on these suggestions: Several days have passed, and I have run the MySQL Tuner. # include all files from the config directory # use it for options that affect everything # This group is read both both by the client and the server
I have a relatively freshly-minted server running AlmaLinux 8.7, with 64GB RAM and a pair of terabyte SSDs.Īfter updating to MariaDB 10.6.x, I configured the my.cnf file to represent a prior server with a similar setup:
0 kommentar(er)
