Advertisement
Guest User

Untitled

a guest
Jul 11th, 2014
216
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.55 KB | None | 0 0
  1. # MySQL Server Instance Configuration File
  2. # ----------------------------------------------------------------------
  3. # Generated by the MySQL Server Instance Configuration Wizard
  4. #
  5. #
  6. # Installation Instructions
  7. # ----------------------------------------------------------------------
  8. #
  9. # On Linux you can copy this file to /etc/my.cnf to set global options,
  10. # mysql-data-dir/my.cnf to set server-specific options
  11. # (@localstatedir@ for this installation) or to
  12. # ~/.my.cnf to set user-specific options.
  13. #
  14. # On Windows you should keep this file in the installation directory
  15. # of your server (e.g. C:\Program Files\MySQL\MySQL Server X.Y). To
  16. # make sure the server reads the config file use the startup option
  17. # "--defaults-file".
  18. #
  19. # To run run the server from the command line, execute this in a
  20. # command line shell, e.g.
  21. # mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
  22. #
  23. # To install the server as a Windows service manually, execute this in a
  24. # command line shell, e.g.
  25. # mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
  26. #
  27. # And then execute this in a command line shell to start the server, e.g.
  28. # net start MySQLXY
  29. #
  30. #
  31. # Guildlines for editing this file
  32. # ----------------------------------------------------------------------
  33. #
  34. # In this file, you can use all long options that the program supports.
  35. # If you want to know the options a program supports, start the program
  36. # with the "--help" option.
  37. #
  38. # More detailed information about the individual options can also be
  39. # found in the manual.
  40. #
  41. #
  42. # CLIENT SECTION
  43. # ----------------------------------------------------------------------
  44. #
  45. # The following options will be read by MySQL client applications.
  46. # Note that only client applications shipped by MySQL are guaranteed
  47. # to read this section. If you want your own MySQL client program to
  48. # honor these values, you need to specify it as an option during the
  49. # MySQL client library initialization.
  50. #
  51. [client]
  52.  
  53. port=3306
  54.  
  55. [mysql]
  56.  
  57. default-character-set=utf8
  58.  
  59.  
  60. # SERVER SECTION
  61. # ----------------------------------------------------------------------
  62. #
  63. # The following options will be read by the MySQL Server. Make sure that
  64. # you have installed the server correctly (see above) so it reads this
  65. # file.
  66. #
  67. [mysqld]
  68.  
  69. # The TCP/IP Port the MySQL Server will listen on
  70. port=3306
  71.  
  72.  
  73. #Path to installation directory. All paths are usually resolved relative to this.
  74. basedir="C:/Program Files/MySQL/MySQL Server 5.5/"
  75.  
  76. #Path to the database root
  77. datadir="C:/ProgramData/MySQL/MySQL Server 5.5/Data/"
  78.  
  79. # The default character set that will be used when a new schema or table is
  80. # created and no character set is defined
  81. character-set-server=utf8
  82.  
  83. # The default storage engine that will be used when create new tables when
  84. default-storage-engine=INNODB
  85.  
  86. # Set the SQL mode to strict
  87. sql-mode="NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
  88.  
  89. # The maximum amount of concurrent sessions the MySQL server will
  90. # allow. One of these connections will be reserved for a user with
  91. # SUPER privileges to allow the administrator to login even if the
  92. # connection limit has been reached.
  93. max_connections=9999999999
  94.  
  95. # Maximum amount of errors allowed per host. If this limit is reached,
  96. # the host will be blocked from connecting to the MySQL server until
  97. # "FLUSH HOSTS" has been run or the server was restarted. Invalid
  98. # passwords and other errors during the connect phase result in
  99. # increasing this value. See the "Aborted_connects" status variable for
  100. # global counter.
  101. max_connect_errors = 99999999999
  102.  
  103. # Query cache is used to cache SELECT results and later return them
  104. # without actual executing the same query once again. Having the query
  105. # cache enabled may result in significant speed improvements, if your
  106. # have a lot of identical queries and rarely changing tables. See the
  107. # "Qcache_lowmem_prunes" status variable to check if the current value
  108. # is high enough for your load.
  109. # Note: In case your tables change very often or if your queries are
  110. # textually different every time, the query cache may result in a
  111. # slowdown instead of a performance improvement.
  112. query_cache_size=0
  113.  
  114. # The maximum size of a query packet the server can handle as well as
  115. # maximum query size server can process (Important when working with
  116. # large BLOBs). enlarged dynamically, for each connection.
  117. max_allowed_packet = 100M
  118.  
  119. # The number of open tables for all threads. Increasing this value
  120. # increases the number of file descriptors that mysqld requires.
  121. # Therefore you have to make sure to set the amount of open files
  122. # allowed to at least 4096 in the variable "open-files-limit" in
  123. # section [mysqld_safe]
  124. table_cache=2048
  125.  
  126. # Maximum size for internal (in-memory) temporary tables. If a table
  127. # grows larger than this value, it is automatically converted to disk
  128. # based table This limitation is for a single table. There can be many
  129. # of them.
  130. tmp_table_size=205M
  131.  
  132.  
  133. # How many threads we should keep in a cache for reuse. When a client
  134. # disconnects, the client's threads are put in the cache if there aren't
  135. # more than thread_cache_size threads from before. This greatly reduces
  136. # the amount of thread creations needed if you have a lot of new
  137. # connections. (Normally this doesn't give a notable performance
  138. # improvement if you have a good thread implementation.)
  139. thread_cache_size=100
  140.  
  141. #*** MyISAM Specific options
  142.  
  143. # The maximum size of the temporary file MySQL is allowed to use while
  144. # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
  145. # If the file-size would be bigger than this, the index will be created
  146. # through the key cache (which is slower).
  147. myisam_max_sort_file_size=100G
  148.  
  149. # If the temporary file used for fast index creation would be bigger
  150. # than using the key cache by the amount specified here, then prefer the
  151. # key cache method. This is mainly used to force long character keys in
  152. # large tables to use the slower key cache method to create the index.
  153. myisam_sort_buffer_size=700M
  154.  
  155. # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
  156. # Do not set it larger than 30% of your available memory, as some memory
  157. # is also required by the OS to cache rows. Even if you're not using
  158. # MyISAM tables, you should still set it to 8-64M as it will also be
  159. # used for internal temporary disk tables.
  160. key_buffer_size=1G
  161.  
  162. # Size of the buffer used for doing full table scans of MyISAM tables.
  163. # Allocated per thread, if a full scan is needed.
  164. read_buffer_size=64K
  165. read_rnd_buffer_size=256K
  166.  
  167. # This buffer is allocated when MySQL needs to rebuild the index in
  168. # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
  169. # into an empty table. It is allocated per thread so be careful with
  170. # large settings.
  171. sort_buffer_size=256K
  172.  
  173.  
  174. #*** INNODB Specific options ***
  175.  
  176.  
  177. # Use this option if you have a MySQL server with InnoDB support enabled
  178. # but you do not plan to use it. This will save memory and disk space
  179. # and speed up some things.
  180. #skip-innodb
  181.  
  182. # Additional memory pool that is used by InnoDB to store metadata
  183. # information. If InnoDB requires more memory for this purpose it will
  184. # start to allocate it from the OS. As this is fast enough on most
  185. # recent operating systems, you normally do not need to change this
  186. # value. SHOW INNODB STATUS will display the current amount used.
  187. innodb_additional_mem_pool_size=50M
  188.  
  189. # If set to 1, InnoDB will flush (fsync) the transaction logs to the
  190. # disk at each commit, which offers full ACID behavior. If you are
  191. # willing to compromise this safety, and you are running small
  192. # transactions, you may set this to 0 or 2 to reduce disk I/O to the
  193. # logs. Value 0 means that the log is only written to the log file and
  194. # the log file flushed to disk approximately once per second. Value 2
  195. # means the log is written to the log file at each commit, but the log
  196. # file is only flushed to disk approximately once per second.
  197. innodb_flush_log_at_trx_commit=1
  198.  
  199. # The size of the buffer InnoDB uses for buffering log data. As soon as
  200. # it is full, InnoDB will have to flush it to disk. As it is flushed
  201. # once per second anyway, it does not make sense to have it very large
  202. # (even with long transactions).
  203. innodb_log_buffer_size=7M
  204.  
  205. # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
  206. # row data. The bigger you set this the less disk I/O is needed to
  207. # access data in tables. On a dedicated database server you may set this
  208. # parameter up to 80% of the machine physical memory size. Do not set it
  209. # too large, though, because competition of the physical memory may
  210. # cause paging in the operating system. Note that on 32bit systems you
  211. # might be limited to 2-3.5G of user level memory per process, so do not
  212. # set it too high.
  213. innodb_buffer_pool_size=26G
  214.  
  215. # Size of each log file in a log group. You should set the combined size
  216. # of log files to about 25%-100% of your buffer pool size to avoid
  217. # unneeded buffer pool flush activity on log file overwrite. However,
  218. # note that a larger logfile size will increase the time needed for the
  219. # recovery process.
  220. innodb_log_file_size=343M
  221.  
  222. # Number of threads allowed inside the InnoDB kernel. The optimal value
  223. # depends highly on the application, hardware as well as the OS
  224. # scheduler properties. A too high value may lead to thread thrashing.
  225. innodb_thread_concurrency=16
  226.  
  227. [mysqld_safe]
  228. # Increase the amount of open files allowed per process. Warning: Make
  229. # sure you have set the global system limit high enough! The high value
  230. # is required for a large number of opened tables
  231. open-files-limit = 65535
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement