· 6 years ago · Mar 23, 2020, 01:32 AM
1# Other default tuning values
2# MySQL Server Instance Configuration File
3# ----------------------------------------------------------------------
4# Generated by the MySQL Server Instance Configuration Wizard
5#
6#
7# Installation Instructions
8# ----------------------------------------------------------------------
9#
10# On Linux you can copy this file to /etc/my.cnf to set global options,
11# mysql-data-dir/my.cnf to set server-specific options
12# (@localstatedir@ for this installation) or to
13# ~/.my.cnf to set user-specific options.
14#
15# On Windows you should keep this file in the installation directory
16# of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
17# make sure the server reads the config file use the startup option
18# "--defaults-file".
19#
20# To run run the server from the command line, execute this in a
21# command line shell, e.g.
22# mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
23#
24# To install the server as a Windows service manually, execute this in a
25# command line shell, e.g.
26# mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
27#
28# And then execute this in a command line shell to start the server, e.g.
29# net start MySQLXY
30#
31#
32# Guildlines for editing this file
33# ----------------------------------------------------------------------
34#
35# In this file, you can use all long options that the program supports.
36# If you want to know the options a program supports, start the program
37# with the "--help" option.
38#
39# More detailed information about the individual options can also be
40# found in the manual.
41#
42# For advice on how to change settings please see
43# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html
44#
45#
46# CLIENT SECTION
47# ----------------------------------------------------------------------
48#
49# The following options will be read by MySQL client applications.
50# Note that only client applications shipped by MySQL are guaranteed
51# to read this section. If you want your own MySQL client program to
52# honor these values, you need to specify it as an option during the
53# MySQL client library initialization.
54#
55[client]
56no-beep
57
58# pipe
59# socket=0.0
60port=3306
61
62[mysql]
63
64default-character-set = utf8
65
66
67# SERVER SECTION
68# ----------------------------------------------------------------------
69#
70# The following options will be read by the MySQL Server. Make sure that
71# you have installed the server correctly (see above) so it reads this
72# file.
73#
74# server_type=2
75[mysqld]
76
77# The next three options are mutually exclusive to SERVER_PORT below.
78# skip-networking
79
80# enable-named-pipe
81
82# shared-memory
83
84# shared-memory-base-name=MYSQL
85
86# The Pipe the MySQL Server will use
87# socket=MYSQL
88
89# The TCP/IP Port the MySQL Server will listen on
90port=3306
91
92# Path to installation directory. All paths are usually resolved relative to this.
93basedir="C:\AppServ/MySQL"
94
95# Path to the database root
96datadir="C:\AppServ/MySQL/data/"
97
98# The default character set that will be used when a new schema or table is
99# created and no character set is defined
100character-set-server = utf8
101
102# The default storage engine that will be used when create new tables when
103# default-storage-engine=INNODB
104
105# Set the SQL mode to strict
106# sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
107sql-mode=""
108
109# Enable Windows Authentication
110# plugin-load=authentication_windows.dll
111
112# General and Slow logging.
113log-output=FILE
114general-log=0
115general_log_file="mysql.log"
116slow-query-log=1
117slow_query_log_file="mysql-slow.log"
118long_query_time=10
119
120# Binary Logging.
121# log-bin
122
123# Error Logging.
124log-error="mysql-error.log"
125
126# Server Id.
127server-id=1
128
129# Secure File Priv.
130secure-file-priv="datadir="C:\AppServ/MySQL/Uploads"
131
132# The maximum amount of concurrent sessions the MySQL server will
133# allow. One of these connections will be reserved for a user with
134# SUPER privileges to allow the administrator to login even if the
135# connection limit has been reached.
136max_connections=400
137
138# Query cache is used to cache SELECT results and later return them
139# without actual executing the same query once again. Having the query
140# cache enabled may result in significant speed improvements, if your
141# have a lot of identical queries and rarely changing tables. See the
142# "Qcache_lowmem_prunes" status variable to check if the current value
143# is high enough for your load.
144# Note: In case your tables change very often or if your queries are
145# textually different every time, the query cache may result in a
146# slowdown instead of a performance improvement.
147query_cache_size=0
148
149# The number of open tables for all threads. Increasing this value
150# increases the number of file descriptors that mysqld requires.
151# Therefore you have to make sure to set the amount of open files
152# allowed to at least 4096 in the variable "open-files-limit" in
153# section [mysqld_safe]
154table_open_cache=5000
155
156# Maximum size for internal (in-memory) temporary tables. If a table
157# grows larger than this value, it is automatically converted to disk
158# based table This limitation is for a single table. There can be many
159# of them.
160tmp_table_size=495M
161
162# How many threads we should keep in a cache for reuse. When a client
163# disconnects, the client's threads are put in the cache if there aren't
164# more than thread_cache_size threads from before. This greatly reduces
165# the amount of thread creations needed if you have a lot of new
166# connections. (Normally this doesn't give a notable performance
167# improvement if you have a good thread implementation.)
168thread_cache_size=10
169
170#*** MyISAM Specific options
171# The maximum size of the temporary file MySQL is allowed to use while
172# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
173# If the file-size would be bigger than this, the index will be created
174# through the key cache (which is slower).
175myisam_max_sort_file_size=100G
176
177# If the temporary file used for fast index creation would be bigger
178# than using the key cache by the amount specified here, then prefer the
179# key cache method. This is mainly used to force long character keys in
180# large tables to use the slower key cache method to create the index.
181myisam_sort_buffer_size=975M
182
183# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
184# Do not set it larger than 30% of your available memory, as some memory
185# is also required by the OS to cache rows. Even if you're not using
186# MyISAM tables, you should still set it to 8-64M as it will also be
187# used for internal temporary disk tables.
188key_buffer_size=8M
189
190# Size of the buffer used for doing full table scans of MyISAM tables.
191# Allocated per thread, if a full scan is needed.
192read_buffer_size=64K
193read_rnd_buffer_size=256K
194
195#*** INNODB Specific options ***
196# innodb_data_home_dir=0.0
197
198# Use this option if you have a MySQL server with InnoDB support enabled
199# but you do not plan to use it. This will save memory and disk space
200# and speed up some things.
201# skip-innodb
202
203# If set to 1, InnoDB will flush (fsync) the transaction logs to the
204# disk at each commit, which offers full ACID behavior. If you are
205# willing to compromise this safety, and you are running small
206# transactions, you may set this to 0 or 2 to reduce disk I/O to the
207# logs. Value 0 means that the log is only written to the log file and
208# the log file flushed to disk approximately once per second. Value 2
209# means the log is written to the log file at each commit, but the log
210# file is only flushed to disk approximately once per second.
211innodb_flush_log_at_trx_commit=1
212
213# The size of the buffer InnoDB uses for buffering log data. As soon as
214# it is full, InnoDB will have to flush it to disk. As it is flushed
215# once per second anyway, it does not make sense to have it very large
216# (even with long transactions).
217innodb_log_buffer_size=1M
218
219# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
220# row data. The bigger you set this the less disk I/O is needed to
221# access data in tables. On a dedicated database server you may set this
222# parameter up to 80% of the machine physical memory size. Do not set it
223# too large, though, because competition of the physical memory may
224# cause paging in the operating system. Note that on 32bit systems you
225# might be limited to 2-3.5G of user level memory per process, so do not
226# set it too high.
227innodb_buffer_pool_size=8M
228
229# Size of each log file in a log group. You should set the combined size
230# of log files to about 25%-100% of your buffer pool size to avoid
231# unneeded buffer pool flush activity on log file overwrite. However,
232# note that a larger logfile size will increase the time needed for the
233# recovery process.
234innodb_log_file_size=48M
235
236# Number of threads allowed inside the InnoDB kernel. The optimal value
237# depends highly on the application, hardware as well as the OS
238# scheduler properties. A too high value may lead to thread thrashing.
239innodb_thread_concurrency=20
240
241# The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
242innodb_autoextend_increment=64
243
244# The number of regions that the InnoDB buffer pool is divided into.
245# For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
246# by reducing contention as different threads read and write to cached pages.
247innodb_buffer_pool_instances=8
248
249# Determines the number of threads that can enter InnoDB concurrently.
250innodb_concurrency_tickets=3000
251
252# Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
253# it can be moved to the new sublist.
254innodb_old_blocks_time=1000
255
256# It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.
257innodb_open_files=300
258
259# When this variable is enabled, InnoDB updates statistics during metadata statements.
260innodb_stats_on_metadata=0
261
262# When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
263# in a separate .ibd file, rather than in the system tablespace.
264innodb_file_per_table=1
265
266# Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
267innodb_checksum_algorithm=0
268
269# The number of outstanding connection requests MySQL can have.
270# This option is useful when the main MySQL thread gets many connection requests in a very short time.
271# It then takes some time (although very little) for the main thread to check the connection and start a new thread.
272# The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
273# stops answering new requests.
274# You need to increase this only if you expect a large number of connections in a short period of time.
275back_log=80
276
277# If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
278# synchronize unflushed data to disk.
279# This option is best used only on systems with minimal resources.
280flush_time=0
281
282# The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
283# indexes and thus perform full table scans.
284join_buffer_size=256K
285
286# The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
287# mysql_stmt_send_long_data() C API function.
288max_allowed_packet=4M
289
290# If more than this many successive connection requests from a host are interrupted without a successful connection,
291# the server blocks that host from performing further connections.
292max_connect_errors=800
293
294# Changes the number of file descriptors available to mysqld.
295# You should try increasing the value of this option if mysqld gives you the error "Too many open files".
296open_files_limit=4161
297
298# Set the query cache type. 0 for OFF, 1 for ON and 2 for DEMAND.
299query_cache_type=0
300
301# If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
302# sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
303# or improved indexing.
304sort_buffer_size=256K
305
306# The number of table definitions (from .frm files) that can be stored in the definition cache.
307# If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
308# The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
309# The minimum and default values are both 400.
310table_definition_cache=1400
311
312# Specify the maximum size of a row-based binary log event, in bytes.
313# Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
314binlog_row_event_max_size=8K
315
316# If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.
317# (using fdatasync()) after every sync_master_info events.
318sync_master_info=10000
319
320# If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
321# (using fdatasync()) after every sync_relay_log writes to the relay log.
322sync_relay_log=10000
323
324# If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.
325# (using fdatasync()) after every sync_relay_log_info transactions.
326sync_relay_log_info=10000