Hi, here is the output from MySQLTuner
General recommendations:
MySQL started within last 24 hours - recommendations may be inaccurate
Reduce or eliminate unclosed connections and network issues
Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
When making adjustments, make tmp_table_size/max_heap_table_size equal
Reduce your SELECT DISTINCT queries which have no LIMIT clause
Set thread_cache_size to 4 as a starting value
Performance should be activated for better diagnostics
Consider installing Sys schema from
https://github.com/mysql/mysql-sys Read this before changing innodb_log_file_size and/or innodb_log_files_in_group:
http://bit.ly/2wgkDvSVariables to adjust:
query_cache_size (=0)
query_cache_type (=0)
query_cache_limit (> 1M, or use smaller result sets)
tmp_table_size (> 16M)
max_heap_table_size (> 16M)
thread_cache_size (start at 4)
performance_schema = ON enable PFS
innodb_log_file_size should be (=16M) if possible, so InnoDB total log files size equals to 25% of buffer pool size.
innodb_buffer_pool_instances (=1)
How do I deal with that? I added the recommendations to adjust variables to /etc/my.cnf just below the line
!includedir /etc/my.cnf.d
[mysqld]
query_cache_size = 0
query_cache_type = 0
query_cache_limit = 3M
tmp_table_size = 32M
max_heap_table_size = 32M
thread_cache_size = 4
performance_schema = ON enable PFS
innodb_log_file_size should be =16M
innodb_buffer_pool_instances =1
Restarting MySQL mariadb.service resulted in database connection errors. is a server reboot necessary or is the syntax not correct?