免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 2120 | 回复: 3
打印 上一主题 下一主题

WIN2003下的MYSQL问题! [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-09-07 06:36 |只看该作者 |倒序浏览
虚拟主机服务器,MYSQL数据库总量约1GB左右。

版本是4.1.14,配置时选择:Dedicated MYSQLSERVER MACHINEMO与Multifunctonal Database模式,最大链接数为1400!

运行中经常出现读取数据缓慢,无法读取等现象。当时系统内存充足,无不良现象!

WINDOWS日志里显示:D:\mysql\bin\mysqld-nt: Forcing close of thread 141660  user: 'a08272046359'

'a08272046359'这里各个数据库名都出现了!

这是2003的兼容性问题还是我的MYSQL没配置好呢?

论坛徽章:
0
2 [报告]
发表于 2005-09-07 08:57 |只看该作者

WIN2003下的MYSQL问题!

ding

论坛徽章:
0
3 [报告]
发表于 2005-09-07 17:52 |只看该作者

WIN2003下的MYSQL问题!


  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 4.1). 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 4.1\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 MySQL41 --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini"
  26. #
  27. # And then execute this in a command line shell to start the server, e.g.
  28. # net start MySQL41
  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. port=3306

  53. default-character-set=latin1


  54. # SERVER SECTION
  55. # ----------------------------------------------------------------------
  56. #
  57. # The following options will be read by the MySQL Server. Make sure that
  58. # you have installed the server correctly (see above) so it reads this
  59. # file.
  60. #
  61. [mysqld]

  62. # The TCP/IP Port the MySQL Server will listen on
  63. port=3306


  64. #Path to installation directory. All paths are usually resolved relative to this.
  65. basedir="D:/mysql/"

  66. #Path to the database root
  67. datadir="D:/mysql/Data/"

  68. # The default character set that will be used when a new schema or table is
  69. # created and no character set is defined
  70. default-character-set=latin1

  71. # The default storage engine that will be used when create new tables when
  72. default-storage-engine=INNODB

  73. # The maximum amount of concurrent sessions the MySQL server will
  74. # allow. One of these connections will be reserved for a user with
  75. # SUPER privileges to allow the administrator to login even if the
  76. # connection limit has been reached.
  77. max_connections=1510

  78. # Query cache is used to cache SELECT results and later return them
  79. # without actual executing the same query once again. Having the query
  80. # cache enabled may result in significant speed improvements, if your
  81. # have a lot of identical queries and rarely changing tables. See the
  82. # "Qcache_lowmem_prunes" status variable to check if the current value
  83. # is high enough for your load.
  84. # Note: In case your tables change very often or if your queries are
  85. # textually different every time, the query cache may result in a
  86. # slowdown instead of a performance improvement.
  87. query_cache_size=146M

  88. # The number of open tables for all threads. Increasing this value
  89. # increases the number of file descriptors that mysqld requires.
  90. # Therefore you have to make sure to set the amount of open files
  91. # allowed to at least 4096 in the variable "open-files-limit" in
  92. # section [mysqld_safe]
  93. table_cache=3020

  94. # Maximum size for internal (in-memory) temporary tables. If a table
  95. # grows larger than this value, it is automatically converted to disk
  96. # based table This limitation is for a single table. There can be many
  97. # of them.
  98. tmp_table_size=27M


  99. # How many threads we should keep in a cache for reuse. When a client
  100. # disconnects, the client's threads are put in the cache if there aren't
  101. # more than thread_cache_size threads from before.  This greatly reduces
  102. # the amount of thread creations needed if you have a lot of new
  103. # connections. (Normally this doesn't give a notable performance
  104. # improvement if you have a good thread implementation.)
  105. thread_cache_size=64

  106. #*** MyISAM Specific options

  107. # The maximum size of the temporary file MySQL is allowed to use while
  108. # recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
  109. # If the file-size would be bigger than this, the index will be created
  110. # through the key cache (which is slower).
  111. myisam_max_sort_file_size=100G

  112. # If the temporary file used for fast index creation would be bigger
  113. # than using the key cache by the amount specified here, then prefer the
  114. # key cache method.  This is mainly used to force long character keys in
  115. # large tables to use the slower key cache method to create the index.
  116. myisam_max_extra_sort_file_size=100G

  117. # If the temporary file used for fast index creation would be bigger
  118. # than using the key cache by the amount specified here, then prefer the
  119. # key cache method.  This is mainly used to force long character keys in
  120. # large tables to use the slower key cache method to create the index.
  121. myisam_sort_buffer_size=27M

  122. # Size of the Key Buffer, used to cache index blocks for MyISAM tables.
  123. # Do not set it larger than 30% of your available memory, as some memory
  124. # is also required by the OS to cache rows. Even if you're not using
  125. # MyISAM tables, you should still set it to 8-64M as it will also be
  126. # used for internal temporary disk tables.
  127. key_buffer_size=224M

  128. # Size of the buffer used for doing full table scans of MyISAM tables.
  129. # Allocated per thread, if a full scan is needed.
  130. read_buffer_size=64K
  131. read_rnd_buffer_size=256K

  132. # This buffer is allocated when MySQL needs to rebuild the index in
  133. # REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
  134. # into an empty table. It is allocated per thread so be careful with
  135. # large settings.
  136. sort_buffer_size=256K


  137. #*** INNODB Specific options ***


  138. # Use this option if you have a MySQL server with InnoDB support enabled
  139. # but you do not plan to use it. This will save memory and disk space
  140. # and speed up some things.
  141. #skip-innodb

  142. # Additional memory pool that is used by InnoDB to store metadata
  143. # information.  If InnoDB requires more memory for this purpose it will
  144. # start to allocate it from the OS.  As this is fast enough on most
  145. # recent operating systems, you normally do not need to change this
  146. # value. SHOW INNODB STATUS will display the current amount used.
  147. innodb_additional_mem_pool_size=9M

  148. # If set to 1, InnoDB will flush (fsync) the transaction logs to the
  149. # disk at each commit, which offers full ACID behavior. If you are
  150. # willing to compromise this safety, and you are running small
  151. # transactions, you may set this to 0 or 2 to reduce disk I/O to the
  152. # logs. Value 0 means that the log is only written to the log file and
  153. # the log file flushed to disk approximately once per second. Value 2
  154. # means the log is written to the log file at each commit, but the log
  155. # file is only flushed to disk approximately once per second.
  156. innodb_flush_log_at_trx_commit=1

  157. # The size of the buffer InnoDB uses for buffering log data. As soon as
  158. # it is full, InnoDB will have to flush it to disk. As it is flushed
  159. # once per second anyway, it does not make sense to have it very large
  160. # (even with long transactions).
  161. innodb_log_buffer_size=5M

  162. # InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
  163. # row data. The bigger you set this the less disk I/O is needed to
  164. # access data in tables. On a dedicated database server you may set this
  165. # parameter up to 80% of the machine physical memory size. Do not set it
  166. # too large, though, because competition of the physical memory may
  167. # cause paging in the operating system.  Note that on 32bit systems you
  168. # might be limited to 2-3.5G of user level memory per process, so do not
  169. # set it too high.
  170. innodb_buffer_pool_size=434M

  171. # Size of each log file in a log group. You should set the combined size
  172. # of log files to about 25%-100% of your buffer pool size to avoid
  173. # unneeded buffer pool flush activity on log file overwrite. However,
  174. # note that a larger logfile size will increase the time needed for the
  175. # recovery process.
  176. innodb_log_file_size=80M

  177. # Number of threads allowed inside the InnoDB kernel. The optimal value
  178. # depends highly on the application, hardware as well as the OS
  179. # scheduler properties. A too high value may lead to thread thrashing.
  180. innodb_thread_concurrency=8
复制代码



以上是我的MY.INI

论坛徽章:
0
4 [报告]
发表于 2005-09-26 01:20 |只看该作者

WIN2003下的MYSQL问题!

ding
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP