[root@mysql support-files]# vim my-small.cnf# Example MySQL config file for small systems.# This is for a system with little memory (<= 64M) where MySQL is only used # from time to time and it's important that the mysqld daemon # doesn't use much resources.

[root@mysql support-files]# vim my-medium.cnf# Example MySQL config file for medium systems.# This is for a system with little memory (32M - 64M) where MySQL plays # an important part, or systems up to 128M where MySQL is used together with # other programs (such as a web server)

[root@mysql support-files]# vim my-large.cnf# Example MySQL config file for large systems. # This is for a large system with memory = 512M where the system runs mainly # MySQL.

[root@mysql support-files]# vim my-huge.cnf# Example MySQL config file for very large systems. # This is for a large system with memory of 1G-2G where the system runs mainly # MySQL.

[root@mysql support-files]# vim my-innodb-heavy-4G.cnf#BEGIN CONFIG INFO #DESCR: 4GB RAM, InnoDB only, ACID, few connections, heavy queries #TYPE: SYSTEM #END CONFIG INFO# This is a MySQL example config file for systems with 4GB of memory # running mostly MySQL using InnoDB only tables and performing complex # queries with few connections.

[root@mysql support-files]# vim my-innodb-heavy-4G.cnf#BEGIN CONFIG INFO #DESCR: 4GB RAM, InnoDB only, ACID, few connections, heavy queries #TYPE: SYSTEM #END CONFIG INFO# # This is a MySQL example config file for systems with 4GB of memory # running mostly MySQL using InnoDB only tables and performing complex # queries with few connections. # # MySQL programs look for option files in a set of # locations which depend on the deployment platform. # You can copy this option file to one of those # locations. For information about these locations, see: # http://dev.mysql.com/doc/mysql/en/option-files.html# # In this file, you can use all long options that a program supports. # If you want to know which options a program supports, run the program # with the "--help" option. # # More detailed information about the individual options can also be # found in the manual. ## # The following options will be read by MySQL client applications. # Note that only client applications shipped by MySQL are guaranteed # to read this section. If you want your own MySQL client program to # honor these values, you need to specify it as an option during the # MySQL client library initialization. ## 以下選項會被MySQL客戶端應(yīng)用讀取, 注意只有MySQL附帶的客戶端應(yīng)用程序保證可以讀取這段內(nèi)容,如果你想你自己的MySQL應(yīng)用程序獲取這些值,需要在MySQL客戶端庫初始化的時候指定這些選項[client] #password  = [your_password] #mysql客戶端連接mysql時的密碼 port    = 3306 #mysql客戶端連接時的默認端口 socket    = /tmp/mysql.sock #與mysql服務(wù)器本地通信所使用的socket文件路徑# *** Application-specific options follow here ***# # The MySQL server # [mysqld]# generic configuration options #一般配置選項 port    = 3306 #mysql服務(wù)器監(jiān)聽的默認端口 socket    = /tmp/mysql.sock #socket本地通信文件路徑# back_log is the number of connections the operating system can keep in # the listen queue, before the MySQL connection manager thread has # processed them. If you have a very high connection rate and experience # "connection refused" errors, you might need to increase this value. # Check your OS documentation for the maximum value of this parameter. # Attempting to set back_log higher than your operating system limit # will have no effect.# back_log 是操作系統(tǒng)在監(jiān)聽隊列中所能保持的連接數(shù), # 隊列保存了在MySQL連接管理器線程處理之前的連接. # 如果你有非常高的連接率并且出現(xiàn)“connection refused”報錯, # 你就應(yīng)該增加此處的值. # 檢查你的操作系統(tǒng)能打開文件數(shù)來獲取這個變量的最大值. # 如果將back_log設(shè)定到比你操作系統(tǒng)限制更高的值,將會沒有效果back_log = 50# Don't listen on a TCP/IP port at all. This can be a security # enhancement, if all processes that need to connect to mysqld run # on the same host. All interaction with mysqld must be made via Unix # sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the "enable-named-pipe" option) will render mysqld useless!# 不在TCP/IP端口上進行監(jiān)聽. # 如果所有的進程都是在同一臺服務(wù)器連接到本地的mysqld, # 這樣設(shè)置將是增強安全的方法 # 所有mysqld的連接都是通過Unix sockets 或者命名管道進行的. # 注意在windows下如果沒有打開命名管道選項而只是用此項 # (通過 “enable-named-pipe” 選項) 將會導致mysql服務(wù)沒有任何作用!#skip-networking #默認是沒有開啟的# The maximum amount of concurrent sessions the MySQL server will # allow. One of these connections will be reserved for a user with # SUPER privileges to allow the administrator to login even if the # connection limit has been reached.# MySQL 服務(wù)器所允許的同時會話數(shù)的上限 # 其中一個連接將被SUPER權(quán)限保留作為管理員登錄. # 即便已經(jīng)達到了連接數(shù)的上限. max_connections = 100# Maximum amount of errors allowed per host. If this limit is reached, # the host will be blocked from connecting to the MySQL server until # "FLUSH HOSTS" has been run or the server was restarted. Invalid # passwords and other errors during the connect phase result in # increasing this value. See the "Aborted_connects" status variable for # global counter.# 每個客戶端連接最大的錯誤允許數(shù)量,如果達到了此限制. # 這個客戶端將會被MySQL服務(wù)阻止直到執(zhí)行了”FLUSH HOSTS” 或者服務(wù)重啟 # 非法的密碼以及其他在鏈接時的錯誤會增加此值. # 查看 “Aborted_connects” 狀態(tài)來獲取全局計數(shù)器. max_connect_errors = 10# The number of open tables for all threads. Increasing this value # increases the number of file descriptors that mysqld requires. # Therefore you have to make sure to set the amount of open files # allowed to at least 4096 in the variable "open-files-limit" in # section [mysqld_safe]# 所有線程所打開表的數(shù)量. # 增加此值就增加了mysqld所需要的文件描述符的數(shù)量 # 這樣你需要確認在[mysqld_safe]中 “open-files-limit” 變量設(shè)置打開文件數(shù)量允許至少2048table_open_cache = 2048# Enable external file level locking. Enabled file locking will have a # negative impact on performance, so only use it in case you have # multiple database instances running on the same files (note some # restrictions still apply!) or if you use other software relying on # locking MyISAM tables on file level.# 允許外部文件級別的鎖. 打開文件鎖會對性能造成負面影響 # 所以只有在你在同樣的文件上運行多個數(shù)據(jù)庫實例時才使用此選項(注意仍會有其他約束!) # 或者你在文件層面上使用了其他一些軟件依賴來鎖定MyISAM表#external-locking #默認是沒有開啟的# The maximum size of a query packet the server can handle as well as # maximum query size server can process (Important when working with # large BLOBs). enlarged dynamically, for each connection.# 服務(wù)所能處理的請求包的最大大小以及服務(wù)所能處理的最大的請求大小(當與大的BLOB字段一起工作時相當必要) # 每個連接獨立的大小.大小動態(tài)增加 max_allowed_packet = 16M# The size of the cache to hold the SQL statements for the binary log # during a transaction. If you often use big, multi-statement # transactions you can increase this value to get more performance. All # statements from transactions are buffered in the binary log cache and # are being written to the binary log at once after the COMMIT. If the # transaction is larger than this value, temporary file on disk is used # instead. This buffer is allocated per connection on first update # statement in transaction# 在一個事務(wù)中binlog為了記錄SQL狀態(tài)所持有的cache大小 # 如果你經(jīng)常使用大的,多聲明的事務(wù),你可以增加此值來獲取更大的性能. # 所有從事務(wù)來的狀態(tài)都將被緩沖在binlog緩沖中然后在提交后一次性寫入到binlog中 # 如果事務(wù)比此值大, 會使用磁盤上的臨時文件來替代. # 此緩沖在每個連接的事務(wù)第一次更新狀態(tài)時被創(chuàng)建 binlog_cache_size = 1M# Maximum allowed size for a single HEAP (in memory) table. This option # is a protection against the accidential creation of a very large HEAP # table which could otherwise use up all memory resources.# 獨立的內(nèi)存表所允許的最大容量. # 此選項為了防止意外創(chuàng)建一個超大的內(nèi)存表導致永盡所有的內(nèi)存資源. max_heap_table_size = 64M# Size of the buffer used for doing full table scans. # Allocated per thread, if a full scan is needed.#MySql讀入緩沖區(qū)大小。對表進行順序掃描的請求將分配一個讀入緩沖區(qū)，MySql會為它分#配一段內(nèi)存緩沖區(qū)。read_buffer_size變量控制這一緩沖區(qū)的大小。如果對表的順序掃描請求非常頻繁，#并且你認為頻繁掃描進行得太慢，可以通過增加該變量值以及內(nèi)存緩沖區(qū)大小提高其性能。 read_buffer_size = 2M# When reading rows in sorted order after a sort, the rows are read # through this buffer to avoid disk seeks. You can improve ORDER BY # performance a lot, if set this to a high value. # Allocated per thread, when needed.#是MySql的隨機讀緩沖區(qū)大小。當按任意順序讀取行時(例如，按照排序順序)，將分配一個隨機讀緩存區(qū)。進行排序查詢時，MySql會首先掃描一遍該緩沖，以避免磁盤搜索，提高查詢速度，如果需#要排序大量數(shù)據(jù)，可適當調(diào)高該值。但MySql會為每個客戶連接發(fā)放該緩沖空間，所以應(yīng)盡量適當設(shè)置該值，以避免內(nèi)存開銷過大。 read_rnd_buffer_size = 16M# Sort buffer is used to perform sorts for some ORDER BY and GROUP BY # queries. If sorted data does not fit into the sort buffer, a disk # based merge sort is used instead - See the "Sort_merge_passes" # status variable. Allocated per thread if sort is needed.# 排序緩沖被用來處理類似ORDER BY以及GROUP BY隊列所引起的排序 # 如果排序后的數(shù)據(jù)無法放入排序緩沖, # 一個用來替代的基于磁盤的合并分類會被使用 # 查看 “Sort_merge_passes” 狀態(tài)變量. # 在排序發(fā)生時由每個線程分配 sort_buffer_size = 8M# This buffer is used for the optimization of full JOINs (JOINs without # indexes). Such JOINs are very bad for performance in most cases # anyway, but setting this variable to a large value reduces the # performance impact. See the "Select_full_join" status variable for a # count of full JOINs. Allocated per thread if full join is found# 此緩沖被使用來優(yōu)化全聯(lián)合(full JOINs 不帶索引的聯(lián)合). # 類似的聯(lián)合在極大多數(shù)情況下有非常糟糕的性能表現(xiàn), # 但是將此值設(shè)大能夠減輕性能影響. # 通過 “Select_full_join” 狀態(tài)變量查看全聯(lián)合的數(shù)量 # 當全聯(lián)合發(fā)生時,在每個線程中分配 join_buffer_size = 8M# How many threads we should keep in a cache for reuse. When a client # disconnects, the client's threads are put in the cache if there aren't # more than thread_cache_size threads from before. This greatly reduces # the amount of thread creations needed if you have a lot of new # connections. (Normally this doesn't give a notable performance # improvement if you have a good thread implementation.)# 我們在cache中保留多少線程用于重用 # 當一個客戶端斷開連接后,如果cache中的線程還少于thread_cache_size, # 則客戶端線程被放入cache中. # 這可以在你需要大量新連接的時候極大的減少線程創(chuàng)建的開銷 # (一般來說如果你有好的線程模型的話,這不會有明顯的性能提升.) thread_cache_size = 8# This permits the application to give the threads system a hint for the # desired number of threads that should be run at the same time. This # value only makes sense on systems that support the thread_concurrency() # function call (Sun Solaris, for example). # You should try [number of CPUs]*(2..4) for thread_concurrency# 此允許應(yīng)用程序給予線程系統(tǒng)一個提示在同一時間給予渴望被運行的線程的數(shù)量. # 此值只對于支持 thread_concurrency() 函數(shù)的系統(tǒng)有意義( 例如Sun Solaris). # 你可可以嘗試使用 [CPU數(shù)量]*(2..4) 來作為thread_concurrency的值 thread_concurrency = 8# Query cache is used to cache SELECT results and later return them # without actual executing the same query once again. Having the query # cache enabled may result in significant speed improvements, if your # have a lot of identical queries and rarely changing tables. See the # "Qcache_lowmem_prunes" status variable to check if the current value # is high enough for your load. # Note: In case your tables change very often or if your queries are # textually different every time, the query cache may result in a # slowdown instead of a performance improvement.# 查詢緩沖常被用來緩沖 SELECT 的結(jié)果并且在下一次同樣查詢的時候不再執(zhí)行直接返回結(jié)果. # 打開查詢緩沖可以極大的提高服務(wù)器速度, 如果你有大量的相同的查詢并且很少修改表. # 查看 “Qcache_lowmem_prunes” 狀態(tài)變量來檢查是否當前值對于你的負載來說是否足夠高. # 注意: 在你表經(jīng)常變化的情況下或者如果你的查詢原文每次都不同, # 查詢緩沖也許引起性能下降而不是性能提升. query_cache_size = 64M# Only cache result sets that are smaller than this limit. This is to # protect the query cache of a very large result set overwriting all # other query results.# 只有小于此設(shè)定值的結(jié)果才會被緩沖 # 此設(shè)置用來保護查詢緩沖,防止一個極大的結(jié)果集將其他所有的查詢結(jié)果都覆蓋.query_cache_limit = 2M# Minimum word length to be indexed by the full text search index. # You might wish to decrease it if you need to search for shorter words. # Note that you need to rebuild your FULLTEXT index, after you have # modified this value.# 被全文檢索索引的最小的字長. # 你也許希望減少它,如果你需要搜索更短字的時候. # 注意在你修改此值之后, # 你需要重建你的 FULLTEXT 索引 ft_min_word_len = 4# If your system supports the memlock() function call, you might want to # enable this option while running MySQL to keep it locked in memory and # to avoid potential swapping out in case of high memory pressure. Good # for performance.# 如果你的系統(tǒng)支持 memlock() 函數(shù),你也許希望打開此選項用以讓運行中的mysql在在內(nèi)存高度緊張的時候,數(shù)據(jù)在內(nèi)存中保持鎖定并且防止可能被swapping out # 此選項對于性能有益 #memlock# Table type which is used by default when creating new tables, if not # specified differently during the CREATE TABLE statement.# 當創(chuàng)建新表時作為默認使用的表類型, # 如果在創(chuàng)建表示沒有特別執(zhí)行表類型,將會使用此值 default-storage-engine = MYISAM# Thread stack size to use. This amount of memory is always reserved at # connection time. MySQL itself usually needs no more than 64K of # memory, while if you use your own stack hungry UDF functions or your # OS requires more stack for some operations, you might need to set this # to a higher value.# 線程使用的堆大小. 此容量的內(nèi)存在每次連接時被預(yù)留. # MySQL 本身常不會需要超過64K的內(nèi)存 # 如果你使用你自己的需要大量堆的UDF函數(shù) # 或者你的操作系統(tǒng)對于某些操作需要更多的堆, # 你也許需要將其設(shè)置的更高一點. thread_stack = 192K# Set the default transaction isolation level. Levels available are:# 設(shè)定默認的事務(wù)隔離級別.可用的級別如下: # READ-UNCOMMITTED, READ-COMMITTED, REPEATABLE-READ, SERIALIZABLE transaction_isolation = REPEATABLE-READ# Maximum size for internal (in-memory) temporary tables. If a table # grows larger than this value, it is automatically converted to disk # based table This limitation is for a single table. There can be many # of them.# 內(nèi)部(內(nèi)存中)臨時表的最大大小 # 如果一個表增長到比此值更大,將會自動轉(zhuǎn)換為基于磁盤的表. # 此限制是針對單個表的,而不是總和. tmp_table_size = 64M# Enable binary logging. This is required for acting as a MASTER in a # replication configuration. You also need the binary log if you need # the ability to do point in time recovery from your latest backup.# 打開二進制日志功能. # 在復(fù)制(replication)配置中,作為MASTER主服務(wù)器必須打開此項 # 如果你需要從你最后的備份中做基于時間點的恢復(fù),你也同樣需要二進制日志. log-bin=mysql-bin# binary logging format - mixed recommended#設(shè)定記錄二進制日志的格式，有三種格式，基于語句 statement、 基于行 row、 混合方式 mixed binlog_format=mixed# If you're using replication with chained slaves (A->B->C), you need to # enable this option on server B. It enables logging of updates done by # the slave thread into the slave's binary log.# 如果你在使用鏈式從服務(wù)器結(jié)構(gòu)的復(fù)制模式 (A->B->C), # 你需要在服務(wù)器B上打開此項. # 此選項打開在從線程上重做過的更新的日志, # 并將其寫入從服務(wù)器的二進制日志. #log_slave_updates# Enable the full query log. Every query (even ones with incorrect # syntax) that the server receives will be logged. This is useful for # debugging, it is usually disabled in production use.# 打開查詢?nèi)罩? 所有的由服務(wù)器接收到的查詢 (甚至對于一個錯誤語法的查詢) # 都會被記錄下來. 這對于調(diào)試非常有用, 在生產(chǎn)環(huán)境中常常關(guān)閉此項. #log #默認是沒有開啟的，會影響服務(wù)器性能# Print warnings to the error log file. If you have any problem with # MySQL you should enable logging of warnings and examine the error log # for possible explanations.# 將警告打印輸出到錯誤log文件. 如果你對于MySQL有任何問題 # 你應(yīng)該打開警告log并且仔細審查錯誤日志,查出可能的原因. #log_warnings# Log slow queries. Slow queries are queries which take more than the # amount of time defined in "long_query_time" or which do not use # indexes well, if log_short_format is not enabled. It is normally good idea # to have this turned on if you frequently add new queries to the # system.# 記錄慢速查詢. 慢速查詢是指消耗了比 “l(fā)ong_query_time” 定義的更多時間的查詢. # 如果 log_long_format 被打開,那些沒有使用索引的查詢也會被記錄. # 如果你經(jīng)常增加新查詢到已有的系統(tǒng)內(nèi)的話. 一般來說這是一個好主意 slow_query_log# All queries taking more than this amount of time (in seconds) will be # trated as slow. Do not use "1" as a value here, as this will result in # even very fast queries being logged from time to time (as MySQL # currently measures time with second accuracy only). # 所有的使用了比這個時間(以秒為單位)更多的查詢會被認為是慢速查詢. # 不要在這里使用”1″, 否則會導致所有的查詢,甚至非常快的查詢頁被記錄下來(由于MySQL 目前時間的精確度只能達到秒的級別).long_query_time = 2# *** Replication related settings # *** 主從復(fù)制相關(guān)的設(shè)置# Unique server identification number between 1 and 2^32-1. This value # is required for both master and slave hosts. It defaults to 1 if # "master-host" is not set, but will MySQL will not function as a master # if it is omitted.# 唯一的服務(wù)辨識號,數(shù)值位于 1 到 2^32-1之間. # 此值在master和slave上都需要設(shè)置. # 如果 “master-host” 沒有被設(shè)置,則默認為1, 但是如果忽略此選項,MySQL不會作為master生效. server-id = 1# Replication Slave (comment out master section to use this) #復(fù)制的Slave (去掉master段的注釋來使其生效) # # To configure this host as a replication slave, you can choose between # two methods : #為了配置此主機作為復(fù)制的slave服務(wù)器,你可以選擇兩種方法: # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - #  the syntax is: #使用 CHANGE MASTER TO 命令 (在我們的手冊中有完整描述) - # 語法如下:# #  CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>, #  MASTER_USER=<user>, MASTER_PASSWORD=<password> ; # #  where you replace <host>, <user>, <password> by quoted strings and #  <port> by the master's port number (3306 by default). #  你需要替換掉 , , 等被尖括號包圍的字段以及使用master的端口號替換 (默認3306). #  Example: 案例 # #  CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, #  MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR 或者 # # 2) Set the variables below. However, in case you choose this method, then #  start replication for the first time (even unsuccessfully, for example #  if you mistyped the password in master-password and the slave fails to #  connect), the slave will create a master.info file, and any later #  changes in this file to the variable values below will be ignored and #  overridden by the content of the master.info file, unless you shutdown #  the slave server, delete master.info and restart the slaver server. #  For that reason, you may want to leave the lines below untouched #  (commented) and instead use CHANGE MASTER TO (see above) ##設(shè)置以下的變量. 不論如何, 在你選擇這種方法的情況下, 然后第一次啟動復(fù)制(甚至不成功的情況下, # 例如如果你輸入錯密碼在master-password字段并且slave無法連接), # slave會創(chuàng)建一個 master.info 文件,并且之后任何對于包含在此文件內(nèi)的參數(shù)的變化都會被忽略 # 并且由 master.info 文件內(nèi)的內(nèi)容覆蓋, 除非你關(guān)閉slave服務(wù), 刪除 master.info 并且重啟slave 服務(wù). # 由于這個原因,你也許不想碰一下的配置(注釋掉的) 并且使用 CHANGE MASTER TO (查看上面) 來代替# required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted# 所需要的唯一id號位于 2 和 2^32 

主站蜘蛛池模板：
玉树县|
桑日县|
安徽省|
梓潼县|
民权县|
灵川县|
桦南县|
云梦县|
和平县|
大方县|
宜阳县|
兰溪市|
徐水县|
通江县|
宁陵县|
吉木乃县|
龙里县|
康保县|
太原市|
尼木县|
微博|
厦门市|
色达县|
疏勒县|
东光县|
明星|
三江|
灌阳县|
松江区|
宁夏|
梨树县|
静海县|
桃江县|
民县|
巴楚县|
二连浩特市|
盐津县|
陆河县|
新余市|
金门县|
无棣县|