qE7JJa5H

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 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# Guidelines 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# https://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]
56
57# pipe=
58
59# socket=MYSQL
60
61port=3306
62
63[mysql]
64no-beep
65
66# default-character-set=
67
68# SERVER SECTION
69# ----------------------------------------------------------------------
70#
71# The following options will be read by the MySQL Server. Make sure that
72# you have installed the server correctly (see above) so it reads this 
73# file.
74#
75# server_type=2
76[mysqld]
77
78# The next three options are mutually exclusive to SERVER_PORT below.
79# skip-networking
80# enable-named-pipe
81# shared-memory
82
83# shared-memory-base-name=MYSQL
84
85# The Pipe the MySQL Server will use
86# socket=MYSQL
87
88# The TCP/IP Port the MySQL Server will listen on
89port=3306
90
91# Path to installation directory. All paths are usually resolved relative to this.
92# basedir="C:/Program Files/MySQL/MySQL Server 5.7/"
93
94# Path to the database root
95datadir=C:/ProgramData/MySQL/MySQL Server 5.7/Data
96
97# The default character set that will be used when a new schema or table is
98# created and no character set is defined
99# character-set-server=
100
101# The default storage engine that will be used when create new tables when
102default-storage-engine=INNODB
103
104# Set the SQL mode to strict
105sql-mode=""
106
107# General and Slow logging.
108log-output=FILE
109
110general-log=0
111
112general_log_file="WIN-QU95NUBGN0O.log"
113
114slow-query-log=1
115
116slow_query_log_file="WIN-QU95NUBGN0O-slow.log"
117
118long_query_time=10
119
120# Error Logging.
121log-error="WIN-QU95NUBGN0O.err"
122
123# ***** Group Replication Related *****
124# Specifies the base name to use for binary log files. With binary logging
125# enabled, the server logs all statements that change data to the binary
126# log, which is used for backup and replication.
127# log-bin
128
129# ***** Group Replication Related *****
130# Sets the binary logging format, and can be any one of STATEMENT, ROW,
131# or MIXED. ROW is suggested for Group Replication.
132# binlog_format
133
134# ***** Group Replication Related *****
135# Causes the master to write a checksum for each event in the binary log.
136# binlog_checksum supports the values NONE (disabled) and CRC32.
137# The default is CRC32. When disabled (value NONE), the server verifies
138# that it is writing only complete events to the binary log by writing
139# and checking the event length (rather than a checksum) for each event.
140# NONE must be used with Group Replication.
141# binlog_checksum
142
143# ***** Group Replication Related *****
144# The base name for the relay log. The server creates relay log files in
145# sequence by adding a numeric suffix to the base name. If you specify this
146# option, the value specified is also used as the base name for the relay log
147# index file. Relay logs increase speed by using load-balancing between disks.
148relay_log="WIN-QU95NUBGN0O-relay"
149
150# ***** Group Replication Related *****
151# Specifies the server ID. For servers that are used in a replication topology,
152# you must specify a unique server ID for each replication server, in the
153# range from 1 to 2^32 − 1. “Unique” means that each ID must be different
154# from every other ID in use by any other replication master or slave.
155server-id=1
156# ***** Group Replication Related *****
157# The host name or IP address of the slave to be reported to the master
158# during slave registration. This value appears in the output of SHOW SLAVE HOSTS
159# on the master server. Leave the value unset if you do not want the slave to
160# register itself with the master.
161# report_host=0.0
162
163# ***** Group Replication Related *****
164# The TCP/IP port number for connecting to the slave, to be reported to the master during
165# slave registration. Set this only if the slave is listening on a nondefault port or if
166# you have a special tunnel from the master or other clients to the slave.
167report_port=3306
168
169# ***** Group Replication Related *****
170# This option specifies whether global transaction identifiers (GTIDs) are
171# used to identify transactions. ON must be used with Group Replication.
172# gtid_mode
173
174# ***** Group Replication Related *****
175# When enabled, the server enforces GTID consistency by allowing execution of
176# only statements that can be safely logged using a GTID. You must set this
177# option to ON before enabling GTID based replication.
178# enforce_gtid_consistency
179
180# ***** Group Replication Related *****
181# Whether updates received by a slave server from a master server should be
182# logged to the slave's own binary log. Binary logging must be enabled on
183# the slave for this variable to have any effect. ON must be used with
184# Group Replication.
185# log_slave_updates
186
187# ***** Group Replication Related *****
188# Determines whether the slave server logs master status and connection information
189# to an InnoDB table in the mysql database, or to a file in the data directory.
190# The TABLE setting is required when multiple replication channels are configured.
191# master_info_repository
192
193# ***** Group Replication Related *****
194# Determines whether the slave server logs its position in the relay logs to an InnoDB
195# table in the mysql database, or to a file in the data directory. The TABLE setting is
196# required when multiple replication channels are configured.
197# relay_log_info_repository
198
199# ***** Group Replication Related *****
200# Defines the algorithm used to hash the writes extracted during a transaction. If you
201# are using Group Replication, this variable must be set to XXHASH64 because the process
202# of extracting the writes from a transaction is required for conflict detection on all
203# group members.
204# transaction_write_set_extraction
205lower_case_table_names=1
206
207# Secure File Priv.
208secure-file-priv="C:/ProgramData/MySQL/MySQL Server 5.7/Uploads"
209
210# The maximum amount of concurrent sessions the MySQL server will
211# allow. One of these connections will be reserved for a user with
212# SUPER privileges to allow the administrator to login even if the
213# connection limit has been reached.
214max_connections=151
215
216# The number of open tables for all threads. Increasing this value
217# increases the number of file descriptors that mysqld requires.
218# Therefore you have to make sure to set the amount of open files
219# allowed to at least 4096 in the variable "open-files-limit" in
220# section [mysqld_safe]
221table_open_cache=2000
222
223# Maximum size for internal (in-memory) temporary tables. If a table
224# grows larger than this value, it is automatically converted to disk
225# based table This limitation is for a single table. There can be many
226# of them.
227tmp_table_size=340M
228
229# How many threads we should keep in a cache for reuse. When a client
230# disconnects, the client's threads are put in the cache if there aren't
231# more than thread_cache_size threads from before.  This greatly reduces
232# the amount of thread creations needed if you have a lot of new
233# connections. (Normally this doesn't give a notable performance
234# improvement if you have a good thread implementation.)
235thread_cache_size=10
236
237#*** MyISAM Specific options
238# The maximum size of the temporary file MySQL is allowed to use while
239# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
240# If the file-size would be bigger than this, the index will be created
241# through the key cache (which is slower).
242myisam_max_sort_file_size=100G
243
244# The size of the buffer that is allocated when sorting MyISAM indexes
245# during a REPAIR TABLE or when creating indexes with CREATE INDEX
246# or ALTER TABLE.
247myisam_sort_buffer_size=666M
248
249# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
250# Do not set it larger than 30% of your available memory, as some memory
251# is also required by the OS to cache rows. Even if you're not using
252# MyISAM tables, you should still set it to 8-64M as it will also be
253# used for internal temporary disk tables.
254key_buffer_size=8M
255
256# Size of the buffer used for doing full table scans of MyISAM tables.
257# Allocated per thread, if a full scan is needed.
258read_buffer_size=64K
259
260read_rnd_buffer_size=256K
261
262#*** INNODB Specific options ***
263# innodb_data_home_dir=
264
265# Use this option if you have a MySQL server with InnoDB support enabled
266# but you do not plan to use it. This will save memory and disk space
267# and speed up some things.
268# skip-innodb
269
270# If set to 1, InnoDB will flush (fsync) the transaction logs to the
271# disk at each commit, which offers full ACID behavior. If you are
272# willing to compromise this safety, and you are running small
273# transactions, you may set this to 0 or 2 to reduce disk I/O to the
274# logs. Value 0 means that the log is only written to the log file and
275# the log file flushed to disk approximately once per second. Value 2
276# means the log is written to the log file at each commit, but the log
277# file is only flushed to disk approximately once per second.
278innodb_flush_log_at_trx_commit=1
279
280# The size of the buffer InnoDB uses for buffering log data. As soon as
281# it is full, InnoDB will have to flush it to disk. As it is flushed
282# once per second anyway, it does not make sense to have it very large
283# (even with long transactions).
284innodb_log_buffer_size=1M
285
286# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
287# row data. The bigger you set this the less disk I/O is needed to
288# access data in tables. On a dedicated database server you may set this
289# parameter up to 80% of the machine physical memory size. Do not set it
290# too large, though, because competition of the physical memory may
291# cause paging in the operating system.  Note that on 32bit systems you
292# might be limited to 2-3.5G of user level memory per process, so do not
293# set it too high.
294innodb_buffer_pool_size=8M
295
296# Size of each log file in a log group. You should set the combined size
297# of log files to about 25%-100% of your buffer pool size to avoid
298# unneeded buffer pool flush activity on log file overwrite. However,
299# note that a larger logfile size will increase the time needed for the
300# recovery process.
301innodb_log_file_size=48M
302
303# Number of threads allowed inside the InnoDB kernel. The optimal value
304# depends highly on the application, hardware as well as the OS
305# scheduler properties. A too high value may lead to thread thrashing.
306innodb_thread_concurrency=9
307
308# The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
309innodb_autoextend_increment=64
310
311# The number of regions that the InnoDB buffer pool is divided into.
312# For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
313# by reducing contention as different threads read and write to cached pages.
314innodb_buffer_pool_instances=8
315
316# Determines the number of threads that can enter InnoDB concurrently.
317innodb_concurrency_tickets=5000
318
319# Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
320# it can be moved to the new sublist.
321innodb_old_blocks_time=1000
322
323# It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.
324innodb_open_files=300
325
326# When this variable is enabled, InnoDB updates statistics during metadata statements.
327innodb_stats_on_metadata=0
328
329# 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
330# in a separate .ibd file, rather than in the system tablespace.
331innodb_file_per_table=1
332
333# 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.
334innodb_checksum_algorithm=0
335
336# The number of outstanding connection requests MySQL can have.
337# This option is useful when the main MySQL thread gets many connection requests in a very short time.
338# It then takes some time (although very little) for the main thread to check the connection and start a new thread.
339# The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
340# stops answering new requests.
341# You need to increase this only if you expect a large number of connections in a short period of time.
342back_log=80
343
344# If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
345# synchronize unflushed data to disk.
346# This option is best used only on systems with minimal resources.
347flush_time=0
348
349# The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
350# indexes and thus perform full table scans.
351join_buffer_size=256K
352
353# The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
354# mysql_stmt_send_long_data() C API function.
355max_allowed_packet=4M
356
357# If more than this many successive connection requests from a host are interrupted without a successful connection,
358# the server blocks that host from performing further connections.
359max_connect_errors=100
360
361# Changes the number of file descriptors available to mysqld.
362# You should try increasing the value of this option if mysqld gives you the error "Too many open files".
363open_files_limit=4161
364
365# If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
366# sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
367# or improved indexing.
368sort_buffer_size=256K
369
370# The number of table definitions (from .frm files) that can be stored in the definition cache.
371# If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
372# The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
373# The minimum and default values are both 400.
374table_definition_cache=1400
375
376# Specify the maximum size of a row-based binary log event, in bytes.
377# Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
378binlog_row_event_max_size=8K
379
380# If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.
381# (using fdatasync()) after every sync_master_info events.
382sync_master_info=10000
383
384# If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
385# (using fdatasync()) after every sync_relay_log writes to the relay log.
386sync_relay_log=10000
387
388# If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.
389# (using fdatasync()) after every sync_relay_log_info transactions.
390sync_relay_log_info=10000
391
392# Load mysql plugins at start."plugin_x ; plugin_y".
393# plugin_load
394
395# The TCP/IP Port the MySQL Server X Protocol will listen on.
396# loose_mysqlx_port=33060