gbY6i1Tn

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