{"id":3251,"date":"2014-11-06T18:49:41","date_gmt":"2014-11-06T18:49:41","guid":{"rendered":"http:\/\/www.deuzebranaweb.com.br\/?p=3251"},"modified":"2014-11-06T18:49:41","modified_gmt":"2014-11-06T18:49:41","slug":"my-ini-mysql-5-6","status":"publish","type":"post","link":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/2014\/11\/06\/my-ini-mysql-5-6\/","title":{"rendered":"my.ini mysql 5.6"},"content":{"rendered":"<p># Other default tuning values<br \/>\n# MySQL Server Instance Configuration File<br \/>\n# &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br \/>\n# Generated by the MySQL Server Instance Configuration Wizard<br \/>\n#<br \/>\n#<br \/>\n# Installation Instructions<br \/>\n# &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br \/>\n#<br \/>\n# On Linux you can copy this file to \/etc\/my.cnf to set global options,<br \/>\n# mysql-data-dir\/my.cnf to set server-specific options<br \/>\n# (@localstatedir@ for this installation) or to<br \/>\n# ~\/.my.cnf to set user-specific options.<br \/>\n#<br \/>\n# On Windows you should keep this file in the installation directory<br \/>\n# of your server (e.g. C:\\Program Files\\MySQL\\MySQL Server X.Y). To<br \/>\n# make sure the server reads the config file use the startup option<br \/>\n# &#8220;&#8211;defaults-file&#8221;.<br \/>\n#<br \/>\n# To run run the server from the command line, execute this in a<br \/>\n# command line shell, e.g.<br \/>\n# mysqld &#8211;defaults-file=&#8221;C:\\Program Files\\MySQL\\MySQL Server X.Y\\my.ini&#8221;<br \/>\n#<br \/>\n# To install the server as a Windows service manually, execute this in a<br \/>\n# command line shell, e.g.<br \/>\n# mysqld &#8211;install MySQLXY &#8211;defaults-file=&#8221;C:\\Program Files\\MySQL\\MySQL Server X.Y\\my.ini&#8221;<br \/>\n#<br \/>\n# And then execute this in a command line shell to start the server, e.g.<br \/>\n# net start MySQLXY<br \/>\n#<br \/>\n#<br \/>\n# Guildlines for editing this file<br \/>\n# &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br \/>\n#<br \/>\n# In this file, you can use all long options that the program supports.<br \/>\n# If you want to know the options a program supports, start the program<br \/>\n# with the &#8220;&#8211;help&#8221; option.<br \/>\n#<br \/>\n# More detailed information about the individual options can also be<br \/>\n# found in the manual.<br \/>\n#<br \/>\n# For advice on how to change settings please see<br \/>\n# http:\/\/dev.mysql.com\/doc\/refman\/5.6\/en\/server-configuration-defaults.html<br \/>\n#<br \/>\n#<br \/>\n# CLIENT SECTION<br \/>\n# &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br \/>\n#<br \/>\n# The following options will be read by MySQL client applications.<br \/>\n# Note that only client applications shipped by MySQL are guaranteed<br \/>\n# to read this section. If you want your own MySQL client program to<br \/>\n# honor these values, you need to specify it as an option during the<br \/>\n# MySQL client library initialization.<br \/>\n#<br \/>\n[client]<br \/>\nno-beep<\/p>\n<p># pipe<br \/>\n# socket=0.0<br \/>\nport=3306<\/p>\n<p>[mysql]<\/p>\n<p>default-character-set=utf8<br \/>\n# SERVER SECTION<br \/>\n# &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br \/>\n#<br \/>\n# The following options will be read by the MySQL Server. Make sure that<br \/>\n# you have installed the server correctly (see above) so it reads this<br \/>\n# file.<br \/>\n#<br \/>\n# server_type=2<br \/>\n[mysqld]<\/p>\n<p># The next three options are mutually exclusive to SERVER_PORT below.<br \/>\n# skip-networking<\/p>\n<p># enable-named-pipe<\/p>\n<p># shared-memory<\/p>\n<p># shared-memory-base-name=MYSQL<\/p>\n<p># The Pipe the MySQL Server will use<br \/>\n# socket=MYSQL<\/p>\n<p># The TCP\/IP Port the MySQL Server will listen on<br \/>\nport=3306<\/p>\n<p># Path to installation directory. All paths are usually resolved relative to this.<br \/>\n# basedir=&#8221;C:\/Program Files\/MySQL\/MySQL Server 5.6\/&#8221;<\/p>\n<p># Path to the database root<br \/>\ndatadir = Z:\/BD\/MySQL\/Ativos<\/p>\n<p># The default character set that will be used when a new schema or table is<br \/>\n# created and no character set is defined<br \/>\ncharacter-set-server=utf8<\/p>\n<p># The default storage engine that will be used when create new tables when<br \/>\ndefault-storage-engine=INNODB<\/p>\n<p># Set the SQL mode to strict<br \/>\nsql-mode=&#8221;STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION&#8221;<\/p>\n<p># Enable Windows Authentication<br \/>\n# plugin-load=authentication_windows.dll<\/p>\n<p># General and Slow logging.<br \/>\nlog-output=FILE<br \/>\ngeneral-log=0<br \/>\ngeneral_log_file=&#8221;WIN-0BF4I0PH3V2.log&#8221;<br \/>\nslow-query-log=1<br \/>\nslow_query_log_file=&#8221;WIN-0BF4I0PH3V2-slow.log&#8221;<br \/>\nlong_query_time=10<\/p>\n<p># Binary Logging.<br \/>\n# log-bin<\/p>\n<p># Error Logging.<br \/>\nlog-error=&#8221;WIN-0BF4I0PH3V2.err&#8221;<\/p>\n<p># Server Id.<br \/>\nserver-id=1<\/p>\n<p># The maximum amount of concurrent sessions the MySQL server will<br \/>\n# allow. One of these connections will be reserved for a user with<br \/>\n# SUPER privileges to allow the administrator to login even if the<br \/>\n# connection limit has been reached.<br \/>\nmax_connections=151<\/p>\n<p># Query cache is used to cache SELECT results and later return them<br \/>\n# without actual executing the same query once again. Having the query<br \/>\n# cache enabled may result in significant speed improvements, if your<br \/>\n# have a lot of identical queries and rarely changing tables. See the<br \/>\n# &#8220;Qcache_lowmem_prunes&#8221; status variable to check if the current value<br \/>\n# is high enough for your load.<br \/>\n# Note: In case your tables change very often or if your queries are<br \/>\n# textually different every time, the query cache may result in a<br \/>\n# slowdown instead of a performance improvement.<br \/>\nquery_cache_size=0<\/p>\n<p># The number of open tables for all threads. Increasing this value<br \/>\n# increases the number of file descriptors that mysqld requires.<br \/>\n# Therefore you have to make sure to set the amount of open files<br \/>\n# allowed to at least 4096 in the variable &#8220;open-files-limit&#8221; in<br \/>\n# section [mysqld_safe]<br \/>\ntable_open_cache=2000<\/p>\n<p># Maximum size for internal (in-memory) temporary tables. If a table<br \/>\n# grows larger than this value, it is automatically converted to disk<br \/>\n# based table This limitation is for a single table. There can be many<br \/>\n# of them.<br \/>\ntmp_table_size=475M<\/p>\n<p># How many threads we should keep in a cache for reuse. When a client<br \/>\n# disconnects, the client&#8217;s threads are put in the cache if there aren&#8217;t<br \/>\n# more than thread_cache_size threads from before. This greatly reduces<br \/>\n# the amount of thread creations needed if you have a lot of new<br \/>\n# connections. (Normally this doesn&#8217;t give a notable performance<br \/>\n# improvement if you have a good thread implementation.)<br \/>\nthread_cache_size=10<\/p>\n<p>#*** MyISAM Specific options<br \/>\n# The maximum size of the temporary file MySQL is allowed to use while<br \/>\n# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.<br \/>\n# If the file-size would be bigger than this, the index will be created<br \/>\n# through the key cache (which is slower).<br \/>\nmyisam_max_sort_file_size=100G<\/p>\n<p># If the temporary file used for fast index creation would be bigger<br \/>\n# than using the key cache by the amount specified here, then prefer the<br \/>\n# key cache method. This is mainly used to force long character keys in<br \/>\n# large tables to use the slower key cache method to create the index.<br \/>\nmyisam_sort_buffer_size=936M<\/p>\n<p># Size of the Key Buffer, used to cache index blocks for MyISAM tables.<br \/>\n# Do not set it larger than 30% of your available memory, as some memory<br \/>\n# is also required by the OS to cache rows. Even if you&#8217;re not using<br \/>\n# MyISAM tables, you should still set it to 8-64M as it will also be<br \/>\n# used for internal temporary disk tables.<br \/>\nkey_buffer_size=8M<\/p>\n<p># Size of the buffer used for doing full table scans of MyISAM tables.<br \/>\n# Allocated per thread, if a full scan is needed.<br \/>\nread_buffer_size=64K<br \/>\nread_rnd_buffer_size=256K<\/p>\n<p># This buffer is allocated when MySQL needs to rebuild the index in<br \/>\n# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE<br \/>\n# into an empty table. It is allocated per thread so be careful with<br \/>\n# large settings.<br \/>\nsort_buffer_size=256K<\/p>\n<p>#*** INNODB Specific options ***<br \/>\n# innodb_data_home_dir=0.0<\/p>\n<p># Use this option if you have a MySQL server with InnoDB support enabled<br \/>\n# but you do not plan to use it. This will save memory and disk space<br \/>\n# and speed up some things.<br \/>\n# skip-innodb<\/p>\n<p># Additional memory pool that is used by InnoDB to store metadata<br \/>\n# information. If InnoDB requires more memory for this purpose it will<br \/>\n# start to allocate it from the OS. As this is fast enough on most<br \/>\n# recent operating systems, you normally do not need to change this<br \/>\n# value. SHOW INNODB STATUS will display the current amount used.<br \/>\ninnodb_additional_mem_pool_size=32M<\/p>\n<p># If set to 1, InnoDB will flush (fsync) the transaction logs to the<br \/>\n# disk at each commit, which offers full ACID behavior. If you are<br \/>\n# willing to compromise this safety, and you are running small<br \/>\n# transactions, you may set this to 0 or 2 to reduce disk I\/O to the<br \/>\n# logs. Value 0 means that the log is only written to the log file and<br \/>\n# the log file flushed to disk approximately once per second. Value 2<br \/>\n# means the log is written to the log file at each commit, but the log<br \/>\n# file is only flushed to disk approximately once per second.<br \/>\ninnodb_flush_log_at_trx_commit=1<\/p>\n<p># The size of the buffer InnoDB uses for buffering log data. As soon as<br \/>\n# it is full, InnoDB will have to flush it to disk. As it is flushed<br \/>\n# once per second anyway, it does not make sense to have it very large<br \/>\n# (even with long transactions).<br \/>\ninnodb_log_buffer_size=16M<\/p>\n<p># InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and<br \/>\n# row data. The bigger you set this the less disk I\/O is needed to<br \/>\n# access data in tables. On a dedicated database server you may set this<br \/>\n# parameter up to 80% of the machine physical memory size. Do not set it<br \/>\n# too large, though, because competition of the physical memory may<br \/>\n# cause paging in the operating system. Note that on 32bit systems you<br \/>\n# might be limited to 2-3.5G of user level memory per process, so do not<br \/>\n# set it too high.<br \/>\ninnodb_buffer_pool_size=4G<\/p>\n<p># Size of each log file in a log group. You should set the combined size<br \/>\n# of log files to about 25%-100% of your buffer pool size to avoid<br \/>\n# unneeded buffer pool flush activity on log file overwrite. However,<br \/>\n# note that a larger logfile size will increase the time needed for the<br \/>\n# recovery process.<br \/>\ninnodb_log_file_size=48M<\/p>\n<p># Number of threads allowed inside the InnoDB kernel. The optimal value<br \/>\n# depends highly on the application, hardware as well as the OS<br \/>\n# scheduler properties. A too high value may lead to thread thrashing.<br \/>\ninnodb_thread_concurrency=17<\/p>\n<p># The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.<br \/>\ninnodb_autoextend_increment=64<\/p>\n<p># The number of regions that the InnoDB buffer pool is divided into.<br \/>\n# For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,<br \/>\n# by reducing contention as different threads read and write to cached pages.<br \/>\ninnodb_buffer_pool_instances=8<\/p>\n<p># Determines the number of threads that can enter InnoDB concurrently.<br \/>\ninnodb_concurrency_tickets=5000<\/p>\n<p># Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before<br \/>\n# it can be moved to the new sublist.<br \/>\ninnodb_old_blocks_time=1000<\/p>\n<p># It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.<br \/>\ninnodb_open_files=300<\/p>\n<p># When this variable is enabled, InnoDB updates statistics during metadata statements.<br \/>\ninnodb_stats_on_metadata=0<\/p>\n<p># 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<br \/>\n# in a separate .ibd file, rather than in the system tablespace.<br \/>\ninnodb_file_per_table=1<\/p>\n<p># 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.<br \/>\ninnodb_checksum_algorithm=0<\/p>\n<p># The number of outstanding connection requests MySQL can have.<br \/>\n# This option is useful when the main MySQL thread gets many connection requests in a very short time.<br \/>\n# It then takes some time (although very little) for the main thread to check the connection and start a new thread.<br \/>\n# The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily<br \/>\n# stops answering new requests.<br \/>\n# You need to increase this only if you expect a large number of connections in a short period of time.<br \/>\nback_log=80<\/p>\n<p># If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and<br \/>\n# synchronize unflushed data to disk.<br \/>\n# This option is best used only on systems with minimal resources.<br \/>\nflush_time=0<\/p>\n<p># The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use<br \/>\n# indexes and thus perform full table scans.<br \/>\njoin_buffer_size=256K<\/p>\n<p># The maximum size of one packet or any generated or intermediate string, or any parameter sent by the<br \/>\n# mysql_stmt_send_long_data() C API function.<br \/>\nmax_allowed_packet=4M<\/p>\n<p># If more than this many successive connection requests from a host are interrupted without a successful connection,<br \/>\n# the server blocks that host from performing further connections.<br \/>\nmax_connect_errors=100<\/p>\n<p># Changes the number of file descriptors available to mysqld.<br \/>\n# You should try increasing the value of this option if mysqld gives you the error &#8220;Too many open files&#8221;.<br \/>\nopen_files_limit=4161<\/p>\n<p># Set the query cache type. 0 for OFF, 1 for ON and 2 for DEMAND.<br \/>\nquery_cache_type=0<\/p>\n<p># If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the<br \/>\n# sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization<br \/>\n# or improved indexing.<br \/>\nsort_buffer_size=256K<\/p>\n<p># The number of table definitions (from .frm files) that can be stored in the definition cache.<br \/>\n# If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.<br \/>\n# The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.<br \/>\n# The minimum and default values are both 400.<br \/>\ntable_definition_cache=1400<\/p>\n<p># Specify the maximum size of a row-based binary log event, in bytes.<br \/>\n# Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.<br \/>\nbinlog_row_event_max_size=8K<\/p>\n<p># If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.<br \/>\n# (using fdatasync()) after every sync_master_info events.<br \/>\nsync_master_info=10000<\/p>\n<p># If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.<br \/>\n# (using fdatasync()) after every sync_relay_log writes to the relay log.<br \/>\nsync_relay_log=10000<\/p>\n<p># If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.<br \/>\n# (using fdatasync()) after every sync_relay_log_info transactions.<br \/>\nsync_relay_log_info=10000<\/p>\n","protected":false},"excerpt":{"rendered":"<p># Other default tuning values # MySQL Server Instance Configuration File # &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;- # Generated by the MySQL Server Instance Configuration Wizard # # # Installation Instructions # &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;- # # On Linux you can copy this file to \/etc\/my.cnf to set global options, #&#8230;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_angie_page":false,"page_builder":"","footnotes":""},"categories":[13],"tags":[],"class_list":["post-3251","post","type-post","status-publish","format-standard","hentry","category-msql"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/posts\/3251","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/comments?post=3251"}],"version-history":[{"count":0,"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/posts\/3251\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/media?parent=3251"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/categories?post=3251"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.deuzebranaweb.com.br\/index.php\/wp-json\/wp\/v2\/tags?post=3251"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}