The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Need help optimizing a 32gb dedicated server

Discussion in 'Workarounds and Optimization' started by doodle10, May 21, 2014.

  1. doodle10

    doodle10 Registered

    Joined:
    May 21, 2014
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Website Owner
    Hello,

    I have a problem with a dedicated server.
    The processor has moments when he is at 200% load.

    my current config is:

    Server configuration: Memory: 32 GB, HDD: 500 GB SSD Processor: Intel(R) Xeon(R) CPU E5-2620 v2 Speed: 2100.004 MHz Cache:15360 KB OS: CentOS 6.5 WHM 11.42.1
    CENTOS 6.5 x86_64 virtuozzo MySQL 5.5.36-cll - MySQL Community Server (GPL)

    bellow i'm putting some setting that are done:

    [mysqld]
    innodb_file_per_table=1
    open_files_limit=50000
    thread_cache_size = 16K
    tmp_table_size = 256M
    max_heap_table_size = 256M
    query_cache_size = 256M
    query_cache_limit = 8M
    table_cache = 4K
    table_definition_cache = 8K
    key_buffer_size = 128M
    join_buffer_size = 12M
    innodb_buffer_pool_size = 8G
    # log_queries_not_using_indexes
    slow_query_log=1
    slow_query_log_file=/var/log/mysql-slow-query.log
    long_query_time=1
    log_error = /var/log/mysql/error.log


    [mysqld_safe]
    log-error=/var/log/mysqld.log


    Using MySQL Tuner I have the following

    mysql tunner.jpg


    Any feedback is great appreciated
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,811
    Likes Received:
    671
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  3. postcd

    postcd Well-Known Member

    Joined:
    Oct 22, 2010
    Messages:
    621
    Likes Received:
    6
    Trophy Points:
    18
    Your mysql config and tunner results looks good. I would use "top -c", "htop" and "iotop -a" commands to see what is happening. Then you can find load causing process. Also try watching log files in /var/log (tail -n50 /var/log/logfilename -f)
     
Loading...

Share This Page