2 Added my.cnf dump together with free memory on server when mySQL service is switched off
source | link

I'm running a large MySQL Database, in the range of 30Gb in size. The MySQL 5.5 server is running on a dedicated server with 60GB of RAM, with no other processes installed apart from monitoring tools, on Debian Wheezy.

I've read around the best way to configure the my.cnf file and opted to increase

innodb_buffer_pool_size = 40G

Adding that to the [mysqld] section of the my.cnf file resulted in the MySQL service failing to reboot. Error log shows no errors. Removing the variable change makes the server load properly.

Am I missing something or doing something that's not supported? If I am, can you point me towards the right direction on how to best optimise the MySQL configuration to make best use of the given memory and CPU processing power (16 CPU Cores). I've looked around but could only find information related to 4 or 8Gb of memory.

my.cnf file contains the following


[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]

user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /var/lib/tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking

bind-address            = 0.0.0.0

key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 192K
thread_cache_size       = 8

myisam-recover         = BACKUP

query_cache_limit       = 1M
query_cache_size        = 16M

expire_logs_days        = 10
max_binlog_size         = 100M


#innodb_buffer_pool_size = 45G

[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]

[isamchk]
key_buffer              = 16M

Memory free on the server when MySQL is switched off is 58GB

I'm running a large MySQL Database, in the range of 30Gb in size. The MySQL 5.5 server is running on a dedicated server with 60GB of RAM, with no other processes installed apart from monitoring tools, on Debian Wheezy.

I've read around the best way to configure the my.cnf file and opted to increase

innodb_buffer_pool_size = 40G

Adding that to the [mysqld] section of the my.cnf file resulted in the MySQL service failing to reboot. Error log shows no errors. Removing the variable change makes the server load properly.

Am I missing something or doing something that's not supported? If I am, can you point me towards the right direction on how to best optimise the MySQL configuration to make best use of the given memory and CPU processing power (16 CPU Cores). I've looked around but could only find information related to 4 or 8Gb of memory.

I'm running a large MySQL Database, in the range of 30Gb in size. The MySQL 5.5 server is running on a dedicated server with 60GB of RAM, with no other processes installed apart from monitoring tools, on Debian Wheezy.

I've read around the best way to configure the my.cnf file and opted to increase

innodb_buffer_pool_size = 40G

Adding that to the [mysqld] section of the my.cnf file resulted in the MySQL service failing to reboot. Error log shows no errors. Removing the variable change makes the server load properly.

Am I missing something or doing something that's not supported? If I am, can you point me towards the right direction on how to best optimise the MySQL configuration to make best use of the given memory and CPU processing power (16 CPU Cores). I've looked around but could only find information related to 4 or 8Gb of memory.

my.cnf file contains the following


[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]

user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /var/lib/tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking

bind-address            = 0.0.0.0

key_buffer              = 16M
max_allowed_packet      = 16M
thread_stack            = 192K
thread_cache_size       = 8

myisam-recover         = BACKUP

query_cache_limit       = 1M
query_cache_size        = 16M

expire_logs_days        = 10
max_binlog_size         = 100M


#innodb_buffer_pool_size = 45G

[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]

[isamchk]
key_buffer              = 16M

Memory free on the server when MySQL is switched off is 58GB

1
source | link

MySQL InnoDB Configuration with 60Gb of Memory

I'm running a large MySQL Database, in the range of 30Gb in size. The MySQL 5.5 server is running on a dedicated server with 60GB of RAM, with no other processes installed apart from monitoring tools, on Debian Wheezy.

I've read around the best way to configure the my.cnf file and opted to increase

innodb_buffer_pool_size = 40G

Adding that to the [mysqld] section of the my.cnf file resulted in the MySQL service failing to reboot. Error log shows no errors. Removing the variable change makes the server load properly.

Am I missing something or doing something that's not supported? If I am, can you point me towards the right direction on how to best optimise the MySQL configuration to make best use of the given memory and CPU processing power (16 CPU Cores). I've looked around but could only find information related to 4 or 8Gb of memory.