Skip to main content

mariadb 10.0.21 very high cpu loads optimization help needed

Comments

8 comments

  • soaringeagle
    additionally, if upgrading to 10.1.8 might help whats the manual upgrade instructions as my server guys will only suport cpanel upgrades wich will not be released for months.. i can;t live with this high cpu usage for months
    0
  • anton_latvia
    well, I also believed that having high limits in MySQL would make server run fast until I run own tests, which showed that average or even default limits would give better performance. Check out my recommendations, I would definitely set most of the limits to lower values.. Optimizing MySQL, Intermediate results - Norsk Webhotell og Domener
    0
  • soaringeagle
    testing it but so far it seems horible why do you not have thread cache enabled
    0
  • soaringeagle
    yea your settings the cpu skyrocketed ram used double what it was using..just to start i have tweaked my settings since posting and it has improved but its not yet where id like it to be
    [mysqld] thread_handling=pool-of-threads wait_timeout = 3800 interactive_timeout = 3800 key_buffer = 1024M max_allowed_packet=268435456 table_cache = 1536 table_definition_cache = 1536 open_files_limit=10000 tmp_table_size = 512M max_heap_table_size = 512M sort_buffer_size =32M read_buffer_size = 8M read_rnd_buffer_size =32M max_connections = 160 innodb_buffer_pool_size = 8G innodb_flush_method = O_DIRECT ft_min_word_len = 3 myisam-recover = BACKUP table_open_cache = 42997 # table_cache = 1024 # thread_concurrency = 8 thread_cache_size =160 # # * Query Cache Configuration # query_cache_limit = 5M query_cache_size = 2G # innodb_file_per_table innodb_log_file_size = 10M innodb_buffer_pool_instances = 8
    i might try 1 or 2 lines from yours see if they help
    0
  • anton_latvia
    well, my tests might have been far your queries. Thread cache I have remove on first tests, but I agree I was too fast to do that, thanks!. ;) but setting it to 160 seems to be overkill. my experience shows, that large key_buffer won't help when you have string selects. I would increate table_cache.. Decrease sort_buffer_size, decrease read_rnd_buffer_size, are you sure you want to have innodb_buffer_pool_size so big? table_open_cache vs table_cache seems to be inadequate.. Also query_cache_size of 2Gb is not good. The way query cache works is that on every update mysql will try to clean old data, so it has to look through 2gb.. I really doubt you get it full at any point. Does stats show that?
    0
  • cPanelMichael
    Hello :) You may also want to run the MySQL tuner after the service has been up for at least 24 hours to get more accurate results. Thank you.
    0
  • soaringeagle
    i think i got it working good now, although at times i still see high spikes but think that might be more from apache
    0
  • cPanelMichael
    The following thread might help if the load spikes stem from Apache: Troubleshooting high server loads on Linux servers Thank you.
    0

Please sign in to leave a comment.