Customer support forums for Atomic Protector (formerly Atomic Secured Linux). There is no such thing as a bad question here as long as it pertains to using Atomic Protector. Newbies feel free to get help getting started or asking questions that may be obvious. Regular users are asked to be gentle.
I've recently noticed that ASL took 15 minutes to load on a high traffic server. Htop shows multiple threads of mysql running at 100%. I ran show full processlist in mysql and this is what is constantly running. Note: The IP keeps changing everytime I run the command
I couldn't run the tests on the main server so i moved the db to a vps with nothing else on it, but on the main server the load usually is at 40-50%. I've changed ASL's dbhost IP to this VPS to troubleshoot.
[mysqld]
local-infile=0
log-warnings=2
query_cache_size=600M
binlog-ignore-db=tortix
datadir = /var/lib/mysql
socket = /var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Settings user and group are ignored when systemd is used (fedora >= 15).
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mysqld according to the
# instructions in http://fedoraproject.org/wiki/Systemd
user=mysql
### MyISAM ###
#key_buffer_size = 600M # keep it low if no myisam data
myisam_recover_options = FORCE,BACKUP
### SAFETY #
#bind_address = 127.0.0.1
local_infile = 0
#innodb = force
max_allowed_packet = 600M
max_connect_errors = 100000
skip_name_resolve
### CACHES AND LIMITS #
back_log = 2000
interactive_timeout = 600
wait_timeout = 600
sort_buffer_size = 1M
read_buffer_size = 1M
#read_rnd_buffer_size = 12M
join_buffer_size = 4M
tmp_table_size = 600M
#max_heap_table_size = 128M
#query_cache_limit = 4M
max_connections = 500
thread_cache_size = 64
open_files_limit = 65535
table_definition_cache = 2048
table_open_cache = 4096
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
Right off the bat, this setting is probably going to cause you problems in general with mysql. Really large query caches can have an counter intuitive inverse effect on performance, as they get really large. In general, you probably dont want to go beyond 128MB. So you may want to lower that to 128M and see how your system performs.
On the VPS, I didnt notice you had a query cache setup, so I'd recommend you setup one there, it will certainly help mysql to have some query cache. Without knowing how much ram your VPS has I couldnt tell you what that should be though.