Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To tune the MySQL please change/add the following setting to the MySQL configuration file, usually /etc/my.cnf or /etc/mysql/my.cnf, below the [mysqld] section:

...

innodb_buffer_pool_size = 
innodb_log_file_size = 
innodb_log_buffer_size = 32M
max_allowed_packet = 

...

32M
max_connections = [threads parameter in server.cfg] * 2 + 1
#innodb_file_per_table = OFF
#innodb_data_file_path = ibdata1:100G;ibdata2:100G:autoextend
#innodb_autoextent_increment = 1000
#query_cache_size = 32MB
#innodb_flush_method = O_DSYNC or O_DIRECT


The innodb_buffer_pool is the memory buffer that InnoDB uses to cache data and indexes of its tables. The larger you set this value, the less disk I/O is needed to access data in tables. On a dedicated Kopano Core server, you may set this to up to 50% of the machine physical memory size. However, do not set it too large because competition for the physical memory might cause paging in the operating system, or even out of memory problems.

The innodb_log_file_size is the size of the transaction log. By default there are two logfiles, but three is recommended. The preferred value size for the log_file_size is 25% of the innodbthe innodb_buffer_pool_size., with 100MB minimum and 1GB maximum

The size of the innodb_log_buffer_size that InnoDB uses to write to the log files on disk. A large log buffer allows large transactions to run without a need to write the log to disk before the transactions commit. If you have big transactions, making the log buffer larger will save disk I/O. This value should be 32Mb.

...