source: npl/commonservers/mysql_conf/root/etc/my.cnf

Last change on this file was c5c522c, checked in by Edwin Eefting <edwin@datux.nl>, 8 years ago

initial commit, transferred from cleaned syn3 svn tree

  • Property mode set to 100644
File size: 2.7 KB
Line 
1### SYN-3 mysql config, optimized for zarafa.
2# (C)2014 DatuX
3
4# The following options will be passed to all MySQL clients
5[client]
6port            = 3306
7socket          = /var/run/mysql/mysql.sock
8
9[mysqld]
10port            = 3306
11socket          = /var/run/mysql/mysql.sock
12key_buffer = 64M
13#table_cache = 64
14sort_buffer_size = 512K
15net_buffer_length = 8K
16read_buffer_size = 256K
17read_rnd_buffer_size = 512K
18myisam_sort_buffer_size = 8M
19thread_stack = 256k
20skip-networking
21
22#dont let mysql decide memory usage (it will be way too much)
23performance_schema = 0
24
25#dont write buffer at each commit
26#http://dev.mysql.com/doc/refman/5.6/en/optimizing-innodb-transaction-management.html
27innodb_flush_log_at_trx_commit = 0
28
29#can safely turn this off because we dont use replication
30#http://dev.mysql.com/doc/refman/5.6/en/optimizing-innodb-transaction-management.html
31innodb_support_xa=0
32
33#innodb_lock_wait_timeout = 50
34max_connections = 500
35
36# neccesary for upgrades according to http://dev.mysql.com/doc/refman/5.1/en/upgrading.html
37innodb_fast_shutdown=0
38
39# default, other settings dont seem to change performance
40#innodb_flush_method=fsync
41
42# this should roughly match the IOPS of the disks.
43# "For systems with individual 5400 RPM or 7200 RPM drives, you might lower the value to the former default of 100."
44innodb_io_capacity=100
45
46# "You might increase this value for a MySQL server with heavy insert, update, and delete activity"
47innodb_change_buffer_max_size=50
48
49# "If a write-intensive workload saturates your I/O capacity, decrease the value, especially if you have a large buffer pool."
50innodb_lru_scan_depth=512
51
52# "A typical setting for a problematic workload might be 1 million, assuming that transactions are small, only 100 bytes in size, and it is permissible to have 100MB of unpurged InnoDB table rows."
53innodb_max_purge_lag=1000000
54
55### SYN-3 zarafa settings for about 1000 users:
56# (based on http://doc.zarafa.com/7.1/Administrator_Manual/en-US/html-single/#_PerformanceTuning )
57
58#"about 50% of RAM size"
59#configured automaticly by run-script:
60innodb_buffer_pool_size = 200000K
61#innodb_buffer_pool_instances = 32
62
63#"32Mb should be enough"
64query_cache_type=1
65query_cache_size=32M
66
67#"25% of the innodb_buffer_pool_size"
68#http://dev.mysql.com/doc/refman/5.6/en/optimizing-innodb-logging.html says: "even as big as the bufferpool."
69innodb_log_file_size = 1G
70
71#"32Mb"
72innodb_log_buffer_size = 32M
73
74#we dont want one huge ibdata-file:
75innodb_file_per_table=1
76
77#at least 16M
78max_allowed_packet = 512M
79
80
81
82[mysqldump]
83quick
84max_allowed_packet = 512M
85
86[mysql]
87no-auto-rehash
88
89[isamchk]
90key_buffer = 20M
91sort_buffer_size = 20M
92read_buffer = 2M
93write_buffer = 2M
94
95[myisamchk]
96key_buffer = 20M
97sort_buffer_size = 20M
98read_buffer = 2M
99write_buffer = 2M
100
101[mysqlhotcopy]
102interactive-timeout
Note: See TracBrowser for help on using the repository browser.