I own a small rig with around 40 diff cpanel accounts, each holding 1 website.
Mostly wordpress.
We use php 7.3 with litespeed.
Recently facing lots of cpu overload with mysql using almost all of it.
This is the cnf file
mysql tuner says
We have mariadb on this.
Can someone who is more familiar on this recommend us what to update to make effective use of this?
Mostly wordpress.
We use php 7.3 with litespeed.
Recently facing lots of cpu overload with mysql using almost all of it.
This is the cnf file
[mysqld]
log-error=/var/lib/mysql/hostname.example.com
performance-schema=0
default-storage-engine=MyISAM
innodb_file_per_table=1
max_allowed_packet=268435456
open_files_limit=10000
local-infile=0
mysql tuner says
Configure your accounts with ip or subnets only, then update your configuration with skip-name-resolve=1
We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found.
See dev.mysql.com/doc/internals/en/join-buffer-size.html
(specially the conclusions at the bottom of the page).
When making adjustments, make tmp_table_size/max_heap_table_size equal
Reduce your SELECT DISTINCT queries which have no LIMIT clause
Performance schema should be activated for better diagnostics
Before changing innodb_log_file_size and/or innodb_log_files_in_group read this: [removed url]
Variables to adjust:
query_cache_size (=0)
query_cache_type (=0)
query_cache_limit (> 1M, or use smaller result sets)
join_buffer_size (> 256.0K, or always use indexes with JOINs)
tmp_table_size (> 16M)
max_heap_table_size (> 16M)
table_definition_cache(400) > 2461 or -1 (autosizing if supported)
performance_schema = ON enable PFS
innodb_buffer_pool_size (>= 565.8M) if possible.
innodb_log_file_size should be (=16M) if possible, so InnoDB total log files size equals to 25% of buffer pool size.We have mariadb on this.
Can someone who is more familiar on this recommend us what to update to make effective use of this?
Last edited by a moderator:
