1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Issues with Server Load, Suggestions...

Discussion in 'Server Configuration and Hosting' started by CivilWarTalk, Oct 28, 2012.

  1. CivilWarTalk

    CivilWarTalk Active Member

    I'm having some issues with my server load, and my server tech sent me this message:

    It almost seems like they are forgetting that I use Innodb.... Any suggestions?
     
  2. Walter

    Walter Well-Known Member

    Please post your my.cnf.

    Parts of your high load are caused by IO (25% WA). Maybe there is no Innodb buffer in your my.cnf and Mysql struggles and has to read all from disk.
     
  3. CivilWarTalk

    CivilWarTalk Active Member

    Code:
    [mysqld]
    local-infile=0
    #skip-innodb
    set-variable = max_connections=300
    safe-show-database
    max_tmp_tables=1
    query_cache_type=1
    query_cache_limit=4M
    query_cache_size=32M
    thread_cache_size=6
    table_cache=475
    tmp_table_size=256M
    max_heap_table_size=256M
    innodb_buffer_pool_size=700M
    interactive_timeout=120
    wait_timeout=120
    key_buffer = 256M
    
     
  4. Walter

    Walter Well-Known Member

    Your Innodb buffer pool is 700 MB but you only have 1000 MB RAM, that won't work :)

    Reduce your Innodb buffer to a reasonable size, e.g. 150 MB. Same for key_buffer, 256 MB if you only have 1000 MB makes no sense.
     
    CyclingTribe and SchmitzIT like this.
  5. CivilWarTalk

    CivilWarTalk Active Member

    I set:

    Code:
    innodb_buffer_pool_size=256M
    key_buffer = 128M
    Loads have been significantly better....
     
  6. CivilWarTalk

    CivilWarTalk Active Member

    If I increase my memory from 960 mb to 1216 mb, how much will that improve this issue? 256 mb doesn't sound like much, but if it makes a difference, maybe I should invest an extra $8 a month and upgrade...
     
  7. CivilWarTalk

    CivilWarTalk Active Member

    Did some additional tweaking today, set:

    innodb_buffer_pool_size=384M
    key_buffer = 32M

    Server seems to respond better under normal loads now. I'll report again after I cycle through our peak load tonight...
     
  8. MattW

    MattW Well-Known Member

    Do you really need 300 max connections as well?
     
  9. CivilWarTalk

    CivilWarTalk Active Member

    No idea, I'm still a novice at setting these options. I assume this was the default setting.
     
  10. MattW

    MattW Well-Known Member

    Maybe try halving it to 150, and that should lower the memory footprint of MySQL quite a bit.
     
  11. hellreturn

    hellreturn Active Member

    IIRC, that wouldn't lower the foot print. It would just tell MySQL DB that 300 max connections is allowed and no more. If his forum uses more then 100 active connections then something isn't right to begin with.

    @OP Download mysqltunner script, run it and post the results. First run the script, then change settings and restart mysql and then again run the script. Post both the outputs.

    https://raw.github.com/rackerhacker/MySQLTuner-perl/master/mysqltuner.pl

    Also might want to change this:

    interactive_timeout=120
    wait_timeout=90
    tmp_table_size=64M
    max_heap_table_size=64M
    max_connections = 75

    max_tmp_tables is not used so you don't need that in config.
     

Share This Page