mysql my-innodb-heavy-4g.cnf_mysql my-innodb-heavy-4G.cnf 配置y详细解读(6)

bulk_insert_buffer_size = 64M

# This buffer is allocated when MySQL needs to rebuild the index in

# REPAIR, OPTIMIZE, ALTER table statements as well as in LOAD DATA INFILE

# into an empty table. It is allocated per thread so be careful with

# large settings.

# 当 MySQL 需要通过 REPAIR、OPTIMIZE、ALTER 表语句重建索引，

# 以及 LOAD DATA INFILE 到一个空表时，该缓冲区被分配。

# 它是给每个线程分配的，因此小心比较大的设置。

myisam_sort_buffer_size = 128M

# The maximum size of the temporary file MySQL is allowed to use while

# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.

# If the file-size would be bigger than this, the index will be created

# through the key cache (which is slower).

# 当重建索引(在 REPAIR、ALTER TABLE 或 LOAD DATA INFILE 期间)时，

# MySQL 允许使用的临时文件的最大大小。

# 如果“file-size”比这个值大，索引将通过键缓存(更慢一些)创建。

myisam_max_sort_file_size = 10G

# If a table has more than one index, MyISAM can use more than one

# thread to repair them by sorting in parallel. This makes sense if you

# have multiple CPUs and plenty of memory.

# 如果一个表有超过一个的索引，MyISAM 能够在排序时并行地使用超过一个的线程来修复它们。

# 如果你有多个 CPU 和足够的内存，这是很有意义的。

myisam_repair_threads = 1

# Automatically check and repair not properly closed MyISAM tables.

# 自动地检查和修复没有正确关闭的 MyISAM 表。

myisam_recover

# *** INNODB Specific options ***

# *** INNODB 特定的选项 ***

# Use this option if you have a MySQL server with InnoDB support enabled

# but you do not plan to use it. This will save memory and disk space

# and speed up some things.

# 如果你有一个支持 InnoDB 启用的 MySQL 服务器，而你却并不计划使用它，请使用该选项。

# 这可以保存一些内存和磁盘空间，并提高速度。

#skip-innodb

# Additional memory pool that is used by InnoDB to store metadata

# information. If InnoDB requires more memory for this purpose it will

# start to allocate it from the OS. As this is fast enough on most

# recent operating systems, you normally do not need to change this

# value. SHOW INNODB STATUS will display the current amount used.

# 附加的内存池，InnoDB 用来存储元数据信息。

# 如果 InnoDB 因该目的而需要更多的内存，它将开始从操作系统来分配它。

# 由于这在大多数最近的操作系统上是足够快的，你通常不需要改变这个值。

# SHOW INNODB STATUS 将显示当前使用总量。

innodb_additional_mem_pool_size = 16M

# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and

# row data. The bigger you set this the less disk I/O is needed to

# access data in tables. On a dedicated database server you may set this

# parameter up to 80% of the machine physical memory size. Do not set it

# too large, though, because competition of the physical memory may

# cause paging in the operating system. Note that on 32bit systems you

# might be limited to 2-3.5G of user level memory per process, so do not

# set it too high.

# InnoDB，不像 MyISAM，使用一个缓冲池来缓存索引和行数据。

# 你将该值设得越大，在表中访问需要的数据时，磁盘 I/O 就越少。

# 在一个专用的数据库服务器上，你可以设置该参数到机器物理内存大小的 80%。

# 不要把它设置得太大，因为物理内存的竞争可能导致操作系统中的分页。

# 注意，在 32 位的系统上，你可能在每个处理器的用户级内存上被限制在 2-3.5G，

# 因此不要把它设置得太高。

innodb_buffer_pool_size = 2G

# InnoDB stores data in one or more data files forming the tablespace.

# If you have a single logical drive for your data, a single

# autoextending file would be good enough. In other cases, a single file

# per device is often a good choice. You can configure InnoDB to use raw

# disk partitions as well - please refer to the manual for more info

# about this.

# InnoDB 存储数据到一个或多个数据文件，形成表空间。

# 如果对于你对你的数据有一个单一的物理设备，那么一个单一的自动扩展文件就已经足够了。

# 在其它情况下，每设备一个单一文件是一个非常好的选择。

# 你也可以配置 InnoDB 来使用原始的磁盘分区 - 请参考手册以获取更多有关这个的信息。

innodb_data_file_path = ibdata1:10M:autoextend

# Set this option if you would like the InnoDB tablespace files to be

# stored in another location. By default this is the MySQL datadir.

# 如果你希望 InnoDB 表空间文件存储到其它的地方，设置该选项。

# 默认的是 MySQL 数据目录。

#innodb_data_home_dir =

# Number of IO threads to use for async IO operations. This value is