i did also recently increase max apasche spare workers start workers etc to what i found recomended for a dedicated server...
in mysql processes i see a ton of 'waitingfor table lock insert into jrcore_cache etc statements
my current mysql settings
[mysqld]
tmp_table_size = 2G
max_heap_table_size = 2G
max_connections = 600
wait_timeout = 200000
interactive_timeout = 200000
key_buffer = 1000M
max_allowed_packet=268435456
thread_cache_size = 8
table_open_cache = 45368
join_buffer_size=2000M
table_cache = 86258
table_definition_cache = 46258
low_priority_updates=1
concurrent_insert=ALWAYS
# * Query Cache Configuration
#
query_cache_limit = 16M
query_cache_size = 128M
table_cache = 2536
# for a 2 Gig RAM droplet
tmp_table_size = 2048M
max_heap_table_size = 2048M
innodb_buffer_pool_size = 4096M
innodb_flush_method = O_DIRECT
open_files_limit=44000
default-storage-engine=MyISAM
innodb_file_per_table=1
table_open_cache=5000
since copying this
low_priority_updates starement was disabled asa test
i believe i ran the integrety check since changing apachy workers but cant be certain
start servers increased from 5 to 25 min spare servers increased from 5 to 25 max spareserervers increased from 10 to 50
--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 07/20/15 10:12:04PM