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.

Optimizing my my.ini

Discussion in 'Workarounds and Optimization' started by hle5128, Nov 7, 2013.

  1. hle5128

    hle5128 Registered

    Joined:
    Nov 7, 2013
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Website Owner
    :confused:

    I'm running wamp on server 2008 with 16G ram and C: is 40G and D: is 130G

    Wamp is being installed on D drive,
    site is running with a lot of connection and logs to mysql

    as right now the largest MYD is name SMS which contains a lot of logs over 7G size.

    Im trying to repair it and take too long, sms table constantly crash and slow.

    I tried to move tmp to D drive but still when doing repair its still saying Repair with keycache

    My goal is optimize the best for my server and also run if efficency and use the max out of my server.


    This is what i have on my.ini setup :


    Code:
    # Example MySQL config file for medium systems.
    #
    # This is for a system with little memory (32M - 64M) where MySQL plays
    # an important part, or systems up to 128M where MySQL is used together with
    # other programs (such as a web server)
    #
    # You can copy this file to
    # /etc/my.cnf to set global options,
    # mysql-data-dir/my.cnf to set server-specific options (in this
    # installation this directory is C:\mysql\data) or
    # ~/.my.cnf to set user-specific options.
    #
    # 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		= /tmp/mysql.sock
    
    # Here follows entries for some specific programs
    
    # The MySQL server
    [wampmysqld]
    port		= 3306
    socket		= /tmp/mysql.sock
    skip-locking
    key_buffer = 16M
    max_allowed_packet = 64M
    table_cache = 512
    sort_buffer_size =1M
    net_buffer_length = 1M
    read_buffer_size = 1M
    read_rnd_buffer_size = 1M
    myisam_sort_buffer_size = 64M
    basedir=D:/wamp/bin/mysql/mysql5.1.36
    log-error=D:/wamp/logs/mysql.log
    datadir=D:/wamp/bin/mysql/mysql5.1.36/data
    
    
    innodb_buffer_pool_size=1G
    
    tmp_table_size=64M
    #tmp_table_size=32M
    
    # 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
    
    # Disable Federated by default
    skip-federated
    
    # 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
    
    # Point the following paths to different dedicated disks
    tmpdir		= D:\mysqltmp	
    #log-update 	= /path-to-dedicated-directory/hostname
    
    # Uncomment the following if you are using InnoDB tables
    
    #innodb_data_home_dir = C:\mysql\data/
    #innodb_data_file_path = ibdata1:10M:autoextend
    #innodb_log_group_home_dir = C:\mysql\data/
    #innodb_log_arch_dir = C:\mysql\data/
    # You can set .._buffer_pool_size up to 50 - 80 %
    # of RAM but beware of setting memory usage too high
    #innodb_buffer_pool_size = 2048M
    innodb_additional_mem_pool_size = 256M
    # Set .._log_file_size to 25 % of buffer pool size
    #innodb_log_file_size = 250M
    #innodb_log_buffer_size = 8M
    #innodb_flush_log_at_trx_commit = 1
    #innodb_lock_wait_timeout = 50
    thread_cache_size=16
    
    [mysqldump]
    quick
    max_allowed_packet = 64M
    
    [mysql]
    no-auto-rehash
    # Remove the next comment character if you are not familiar with SQL
    #safe-updates
    
    [isamchk]
    key_buffer = 20M
    sort_buffer_size = 20M
    read_buffer = 2M
    write_buffer = 2M
    
    [myisamchk]
    key_buffer = 20M
    sort_buffer_size = 20M
    read_buffer = 2M
    write_buffer = 2M
    
    [mysqlhotcopy]
    interactive-timeout
    
    [mysqld]
    port=3306
    max_connections=1400
    #max_connections=1400
    wait_timeout =120


    and this is what MYSQL Tunner say:

    Code:
    	MySQL Tuner 0.6 - Peter Chapman <peter@conglomo.co.nz>
    	Currently running supported MySQL version 5.1.36-community
    	Operating on 64-bit architecture
    	Archive Engine Installed
    	Berkeley DB Engine Not Installed
    	Federated Engine Not Installed
    	InnoDB Engine Not Installed
    	ISAM Engine Not Installed
    	NDBCLUSTER Engine Not Installed
    	Data in MyISAM tables: 9G (Tables: 99)
    	Total fragmented tables: 3
    	All database users have passwords assigned
    	Up for: 26m 25s (141K q [89.000 qps], 583 conn, TX: 297M, RX: 82M)
    	Reads / Writes: 64% / 36%
    	Total buffers: 32.0M global + 3.3M per thread (1400 max threads)
    	Maximum possible memory usage: 4.6G (28% of installed RAM)
    	Slow queries: 1% (496/141K)
    	Highest usage of available connections: 5% (65/1400)
    	Key buffer size / total MyISAM indexes: 16.0M/315.8M
    	Key buffer hit rate: 98% (26M cached / 330K reads)
    	Query cache is disabled
    	Sorts requiring temporary tables: 1% (1 temp sorts / 386 sorts)
    	Temporary tables created on disk: 7% (96 on disk / 1K total)
    	Thread cache hit rate: 88% (65 created / 583 connections)
    	Table cache hit rate: 90% (173 open / 192 opened)
    	Open file limit used: 14% (297/2K)
    	Table locks acquired immediately: 96% (114K immediate / 118K locks)
    	Run OPTIMIZE TABLE to defragment tables for better performance
    	MySQL started within last 24 hours - recommendations may be inaccurate
    	Enable the slow query log to troubleshoot bad queries
    	query_cache_size (>= 8M)
    	Scan Complete
     
  2. thinkbot

    thinkbot Well-Known Member

    Joined:
    Oct 30, 2012
    Messages:
    326
    Likes Received:
    0
    Trophy Points:
    16
    cPanel Access Level:
    Root Administrator
    Correct those:

    key_buffer = 2G # for the future, we set it higher, normally in your case minimum 315 M, higher then MyISAM indexes size

    net_buffer_length = 1M - remove that line

    join_buffer_size = 1M
    sort_buffer_size = 256K
    read_buffer_size = 128K
    read_rnd_buffer_size = 2M

    query_cache_type = 1
    query_cache_size = 50M
    query_cache_limit = 1M

    myisam_sort_buffer_size = 1024M # thats the variable used during myisam table repair/optimize etc.

    max_heap_table_size = 64M
    tmp_table_size = 64M

    slow_query_log=1
    slow_query_log_file=mysql-slow.log
    long_query_time=0.1

    max_connections = 200 # you didnt use more than 65 tops anyways, and thats with your current quite bad config




    InnoDB settings doesnt matter, couse you are not using it anyways
     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Are you using Enkompass or is this just a Windows server without a cPanel product? Note that the MySQL tuner shows that MySQL was running for 26 minutes. Typically you should let it run at least 24 hours before running the tuner to ensure more accurate results.

    Thank you.
     
  4. hle5128

    hle5128 Registered

    Joined:
    Nov 7, 2013
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Website Owner

    hi ,
    thank you for your response.

    the reason it was up running short period of time was due from reboot (mysql crash and freeze when doing myisam check and repair)

    Im trying your configure and let it run for 24h see how it goes.

    This is the window server, without cpanel product
     
  5. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Please keep in mind that these forums are intended to assist users that are using cPanel. There will likely not be much user feedback here for issues that are not related to cPanel or assistance with non-cPanel servers.

    Thank you.
     
Loading...

Share This Page