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.

New server high load

Discussion in 'Workarounds and Optimization' started by screege, Jan 18, 2012.

  1. screege

    screege Well-Known Member

    Joined:
    Aug 11, 2004
    Messages:
    186
    Likes Received:
    0
    Trophy Points:
    16
    High I just migrated to a new box, which is the same than my olda box except it has double ram (4 gb) and double hd, I migrated every single site using whm migration from one server to another and also I used conffigserver cpanel + mailoscanner package,I also copied manually one boxes whm config to athe new one manually the thing is that sometimes at peak hours the load goes to 70% or more on the new box crashing it.

    root@server1 [~]# vmstat 5 5
    procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
    r b swpd free buff cache si so bi bo in cs us sy id wa st
    1 0 108 211968 126340 2835864 0 0 1033 1020 32 194 7 1 78 13 0
    1 0 108 211108 126376 2835868 0 0 0 90 1058 1523 26 0 73 0 0
    1 0 108 212416 126460 2835892 0 0 6 226 1139 1726 28 1 70 0 0
    2 0 108 211796 126528 2836108 0 0 54 178 1112 1727 27 1 72 0 0
    1 0 108 211192 126560 2836164 0 0 0 178 1085 1648 27 1 72 0 0


    # This is for a large system with memory = 512M where the system runs mainly
    # MySQL.
    #
    # MySQL programs look for option files in a set of
    # locations which depend on the deployment platform.
    # You can copy this option file to one of those
    # locations. For information about these locations, see:
    # MySQL :: MySQL 5.5 Reference Manual :: 4.2.3.3 Using Option Files
    #
    # In this file, you can use all long options that a program supports.
    # If you want to know which options a program supports, run the program
    # with the "--help" option.

    # The following options will be passed to all MySQL clients
    [client]
    #password = your_password
    port = 3306
    socket = /var/lib/mysql/mysql.sock

    # Here follows entries for some specific programs

    # The MySQL server
    [mysqld]
    local-infile=0 # security tweak
    max_connections = 250 # cPanel default is 500
    max_allowed_packet = 16M # Default 1M
    wait_timeout = 250

    slow-query-log # because inquiring minds want to know.
    long-query-time = 5 # Default 10

    ####### Performance Tweaks #######
    thread_cache_size = 64 # Default 0
    table_open_cache = 1024 # Default 64
    table_definition_cache = 512 # Default 256
    max_heap_table_size = 128M # Default 16M
    tmp_table_size = 128M # Default 16M (can't be bigger than max_heap_table_size)

    key_buffer_size = 128M # Default 8M
    sort_buffer_size = 256K # Default 2M
    join_buffer_size = 512K # Default 128K
    read_buffer_size = 256K # Default 128K.
    # read_rnd_buffer_size = 512K # Default 256K.
    concurrent_insert = 2 # Deafult 1

    query_cache_limit = 512K # Default 1M
    query_cache_size = 64M # Default 0

    ######### End Performance Tweaks ##########

    # Don't listen on a TCP/IP port at all. This can be a security enhancement,
    # if all processes that need to connect to mysqld run on the same host.
    # All interaction with mysqld must be made via Unix sockets or named pipes.
    # Note that using this option without enabling named pipes on Windows
    # (via the "enable-named-pipe" option) will render mysqld useless!
    #
    #skip-networking

    # Replication Master Server (default)
    # binary logging is required for replication
    #log-bin=mysql-bin

    # binary logging format - mixed recommended
    #binlog_format=mixed

    # required unique id between 1 and 2^32 - 1
    # defaults to 1 if master-host is not set
    # but will not function as a master if omitted
    server-id = 1

    # Replication Slave (comment out master section to use this)
    #
    # To configure this host as a replication slave, you can choose between
    # two methods :
    #
    # 1) Use the CHANGE MASTER TO command (fully described in our manual) -
    # the syntax is:
    #
    # CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
    # MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
    #
    # where you replace <host>, <user>, <password> by quoted strings and
    # <port> by the master's port number (3306 by default).
    #
    # Example:
    #
    # CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
    # MASTER_USER='joe', MASTER_PASSWORD='secret';
    #
    # OR
    #
    # 2) Set the variables below. However, in case you choose this method, then
    # start replication for the first time (even unsuccessfully, for example
    # if you mistyped the password in master-password and the slave fails to
    # connect), the slave will create a master.info file, and any later
    # change in this file to the variables' values below will be ignored and
    # overridden by the content of the master.info file, unless you shutdown
    # the slave server, delete master.info and restart the slaver server.
    # For that reason, you may want to leave the lines below untouched
    # (commented) and instead use CHANGE MASTER TO (see above)
    #
    # required unique id between 2 and 2^32 - 1
    # (and different from the master)
    # defaults to 2 if master-host is set
    # but will not function as a slave if omitted
    #server-id = 2
    #
    # The replication master for this slave - required
    #master-host = <hostname>
    #
    # The username the slave will use for authentication when connecting
    # to the master - required
    #master-user = <username>
    #
    # The password the slave will authenticate with when connecting to
    # the master - required
    #master-password = <password>
    #
    # The port the master is listening on.
    # optional - defaults to 3306
    #master-port = <port>
    #
    # binary logging - not required for slaves, but recommended
    #log-bin=mysql-bin

    # Uncomment the following if you are using InnoDB tables
    #innodb_data_home_dir = /var/lib/mysql
    #innodb_data_file_path = ibdata1:10M:autoextend
    #innodb_log_group_home_dir = /var/lib/mysql
    # You can set .._buffer_pool_size up to 50 - 80 %
    # of RAM but beware of setting memory usage too high
    innodb_buffer_pool_size = 256M
    #innodb_additional_mem_pool_size = 20M
    # Set .._log_file_size to 25 % of buffer pool size
    #innodb_log_file_size = 64M
    #innodb_log_buffer_size = 8M
    #innodb_flush_log_at_trx_commit = 1
    #innodb_lock_wait_timeout = 50

    [mysqldump]
    quick
    max_allowed_packet = 16M

    [mysql]
    no-auto-rehash
    # Remove the next comment character if you are not familiar with SQL
    #safe-updates

    [myisamchk]
    key_buffer_size = 128M
    sort_buffer_size = 128M
    read_buffer = 2M
    write_buffer = 2M

    [mysqlhotcopy]
    interactive-timeout


    Regards
     
  2. alphawolf50

    alphawolf50 Well-Known Member

    Joined:
    Apr 28, 2011
    Messages:
    186
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Hi Screege,

    In the future, please post any output in CODE tags, as it makes it far easier to read. Please post a mysqltuner report as well.

    Thanks,
     
  3. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Also, can you revise your /etc/my.cnf to remove all those comments (the lines with # in front of them). If you want to make a backup to have the comments, please feel free to do so, but a slew of commented out lines makes the file difficult to read. It shouldn't be a massive file but a simple set of some changed variables.
     
  4. screege

    screege Well-Known Member

    Joined:
    Aug 11, 2004
    Messages:
    186
    Likes Received:
    0
    Trophy Points:
    16
    Hi I contacted syslint (www.syslint.com) from the cpanel authorized vendors, they putted an apache alternative called nginx, memcache and revised an rebuilded almost everything and now the server is blazing fast (hope stable too) their response has been great and they actually do the jobs pretty quick.

    Thanks in advanced
     
    #4 screege, Jan 19, 2012
    Last edited: Jan 19, 2012
Loading...

Share This Page