本文转载自：http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html
InnoDB Startup Options and System Variables
This section describes the InnoDB-related command options and system variables.
-
System variables that are true or false can be enabled at server startup by naming them, or disabled by using a
--skip-prefix. For example, to enable or disableInnoDBchecksums, you can use--innodb_checksumsor--skip-innodb_checksumson the command line, orinnodb_checksumsorskip-innodb_checksumsin an option file. -
System variables that take a numeric value can be specified as
--on the command line or asvar_name=valuevar_name=value -
Many system variables can be changed at runtime (see Section 5.1.5.2, “Dynamic System Variables”).
-
For information about
GLOBALandSESSIONvariable scope modifiers, refer to theSETstatement documentation. -
Certain options control the locations and layout of the
InnoDBdata files. Section 14.6, “InnoDBConfiguration” explains how to use these options. -
Some options, which you might not use initially, help tune
InnoDBperformance characteristics based on machine capacity and your databaseworkload. -
For more information on specifying options and system variables, see Section 4.2.3, “Specifying Program Options”.
Table 14.4 InnoDB Option/Variable Reference
InnoDB Command Options
-
Deprecated 5.5.22 Command-Line Format --ignore-builtin-innodbOption-File Format ignore-builtin-innodbSystem Variable Name ignore_builtin_innodbVariable Scope Global Dynamic Variable No Permitted Values Type booleanIn MySQL 5.1, this option caused the server to behave as if the built-in
InnoDBwere not present, which enabledInnoDB Pluginto be used instead. In MySQL 5.5,InnoDBis the default storage engine andInnoDB Pluginis not used, so this option has no effect. As of MySQL 5.5.22, it is deprecated and its use results in a warning. -
Controls loading of the
InnoDBstorage engine, if the server was compiled withInnoDBsupport. This option has a tristate format, with possible values ofOFF,ON, orFORCE. See Section 5.1.8.1, “Installing and Uninstalling Plugins”.To disable
InnoDB, use--innodb=OFFor--skip-innodb. In this case, because the default storage engine isInnoDB, the server will not start unless you also use--default-storage-engineto set the default to some other engine. -
Command-Line Format --innodb-status-fileOption-File Format innodb-status-filePermitted Values Type booleanDefault OFFControls whether
InnoDBcreates a file namedinnodb_status.in the MySQL data directory. If enabled,pidInnoDBperiodically writes the output ofSHOW ENGINE INNODB STATUSto this file.By default, the file is not created. To create it, start mysqld with the
--innodb-status-file=1option. The file is deleted during normal shutdown. -
Disable the
InnoDBstorage engine. See the description of--innodb.
InnoDB System Variables
-
Deprecated 5.5.22 Command-Line Format --ignore-builtin-innodbOption-File Format ignore-builtin-innodbSystem Variable Name ignore_builtin_innodbVariable Scope Global Dynamic Variable No Permitted Values Type booleanSee the description of
--ignore-builtin-innodbunder “InnoDBCommand Options” earlier in this section. -
Command-Line Format --innodb_adaptive_flushing=#Option-File Format innodb_adaptive_flushingSystem Variable Name innodb_adaptive_flushingVariable Scope Global Dynamic Variable Yes Permitted Values Type booleanDefault ONSpecifies whether to dynamically adjust the rate of flushing dirty pages in the
InnoDBbuffer pool based on the workload. Adjusting the flush rate dynamically is intended to avoid bursts of I/O activity. This setting is enabled by default. SeeSection 14.16.2.2, “Configuring the Rate ofInnoDBBuffer Pool Flushing” for more information. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”. -
Command-Line Format --innodb_adaptive_hash_index=#Option-File Format innodb_adaptive_hash_indexSystem Variable Name innodb_adaptive_hash_indexVariable Scope Global Dynamic Variable Yes Permitted Values Type booleanDefault ONWhether the
InnoDBadaptive hash index is enabled or disabled. It may be desirable, depending on your workload, to dynamically enable or disableadaptive hash indexing to improve query performance. Because the adaptive hash index may not be useful for all workloads, conduct benchmarks with it both enabled and disabled, using realistic workloads. SeeSection 14.5.13.5, “Adaptive Hash Indexes” for details.This variable is enabled by default. As of MySQL 5.5, You can modify this parameter using the
SET GLOBALstatement, without restarting the server. Changing the setting requires theSUPERprivilege. You can also use--skip-innodb_adaptive_hash_indexat server startup to disable it.Disabling the adaptive hash index empties the hash table immediately. Normal operations can continue while the hash table is emptied, and executing queries that were using the hash table access the index B-trees directly instead. When the adaptive hash index is re-enabled, the hash table is populated again during normal operation.
-
innodb_additional_mem_pool_sizeCommand-Line Format --innodb_additional_mem_pool_size=#Option-File Format innodb_additional_mem_pool_sizeSystem Variable Name innodb_additional_mem_pool_sizeVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 8388608Range 2097152 .. 4294967295The size in bytes of a memory pool
InnoDBuses to storedata dictionary information and other internal data structures. The more tables you have in your application, the more memory you need to allocate here. IfInnoDBruns out of memory in this pool, it starts to allocate memory from the operating system and writes warning messages to the MySQL error log. The default value is 8MB.This variable relates to the
InnoDBinternal memory allocator, which is unused ifinnodb_use_sys_mallocis enabled. -
Command-Line Format --innodb_autoextend_increment=#Option-File Format innodb_autoextend_incrementSystem Variable Name innodb_autoextend_incrementVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 64Range 1 .. 1000The increment size (in MB) for extending the size of an auto-extending system tablespace file when it becomes full. The default value is 8. This variable does not affect the per-table tablespace files that are created if you use
innodb_file_per_table=1. Those files are auto-extending regardless of the value ofinnodb_autoextend_increment. The initial extensions are by small amounts, after which extensions occur in increments of 4MB. -
Command-Line Format --innodb_autoinc_lock_mode=#Option-File Format innodb_autoinc_lock_modeSystem Variable Name innodb_autoinc_lock_modeVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 1Valid Values 012The lock mode to use for generating auto-increment values. The permissible values are 0, 1, or 2, for “traditional”, “consecutive”, or“interleaved” lock mode, respectively.Section 14.9.5, “
AUTO_INCREMENTHandling inInnoDB”, describes the characteristics of these modes.This variable has a default of 1 (“consecutive” lock mode).
-
Introduced 5.5.4 Command-Line Format --innodb_buffer_pool_instances=#Option-File Format innodb_buffer_pool_instancesSystem Variable Name innodb_buffer_pool_instancesVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 1Range 1 .. 64The number of regions that the
InnoDBbuffer pool is divided into. For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency, by reducing contention as different threads read and write to cached pages. Each page that is stored in or read from the buffer pool is assigned to one of the buffer pool instances randomly, using a hashing function. Each buffer pool manages its own free lists, flush lists, LRUs, and all other data structures connected to a buffer pool, and is protected by its own buffer pool mutex.This option takes effect only when you set the
innodb_buffer_pool_sizeto a size of 1 gigabyte or more. The total size you specify is divided among all the buffer pools. For best efficiency, specify a combination ofinnodb_buffer_pool_instancesandinnodb_buffer_pool_sizeso that each buffer pool instance is at least 1 gigabyte. -
Command-Line Format --innodb_buffer_pool_size=#Option-File Format innodb_buffer_pool_sizeSystem Variable Name innodb_buffer_pool_sizeVariable Scope Global Dynamic Variable No Permitted Values Platform Bit Size 32Type numericDefault 134217728Range 5242880 .. 2**32-1Permitted Values Platform Bit Size 64Type numericDefault 134217728Range 5242880 .. 2**64-1The size in bytes of the buffer pool, the memory area where
InnoDBcaches table and index data. The default value is 128MB. The maximum value depends on the CPU architecture; the maximum is 4294967295 (232-1) on 32-bit systems and 18446744073709551615 (264-1) on 64-bit systems. On 32-bit systems, the CPU architecture and operating system may impose a lower practical maximum size than the stated maximum. When the size of the buffer pool is greater than 1GB, settinginnodb_buffer_pool_instancesto a value greater than 1 can improve the scalability on a busy server.The larger you set this value, the less disk I/O is needed to access the same data in tables more than once. On a dedicated database server, you might set this to up to 80% of the machine physical memory size. Be prepared to scale back this value if these other issues occur:
-
Competition for physical memory might cause paging in the operating system.
-
InnoDBreserves additional memory for buffers and control structures, so that the total allocated space is approximately 10% greater than the specified size. -
The address space must be contiguous, which can be an issue on Windows systems with DLLs that load at specific addresses.
-
The time to initialize the buffer pool is roughly proportional to its size. On large installations, this initialization time might be significant. For example, on a modern Linux x86_64 server, initialization of a 10GB buffer pool takes approximately 6 seconds. See Section 8.9.1, “The
InnoDBBuffer Pool”.
-
-
Command-Line Format --innodb_change_buffering=#Option-File Format innodb_change_bufferingSystem Variable Name innodb_change_bufferingVariable Scope Global Dynamic Variable Yes Permitted Values (<= 5.5.3) Type enumerationDefault insertsValid Values insertsnonePermitted Values (>= 5.5.4) Type enumerationDefault allValid Values insertsdeletespurgeschangesallnoneWhether
InnoDBperforms change buffering, an optimization that delays write operations to secondary indexes so that the I/O operations can be performed sequentially. The permitted values areinserts(buffer insert operations),deletes(buffer delete operations; strictly speaking, the writes that mark index records for later deletion during a purge operation),changes(buffer insert and delete-marking operations),purges(buffer purge operations, the writes when deleted index entries are finally garbage-collected),all(buffer insert, delete-marking, and purge operations) andnone(do not buffer any operations). The default isall. For details, see Section 14.16.5, “ConfiguringInnoDBChange Buffering”. -
Command-Line Format --innodb_checksumsOption-File Format innodb_checksumsSystem Variable Name innodb_checksumsVariable Scope Global Dynamic Variable No Permitted Values Type booleanDefault ONInnoDBcan use checksum validation on all pages read from the disk to ensure extra fault tolerance against broken hardware or data files. This validation is enabled by default. However, under some rare circumstances (such as when running benchmarks) this extra safety feature is unneeded and can be disabled with--skip-innodb-checksums. -
Command-Line Format --innodb_commit_concurrency=#Option-File Format innodb_commit_concurrencySystem Variable Name innodb_commit_concurrencyVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 0Range 0 .. 1000The number of threads that can commit at the same time. A value of 0 (the default) permits any number of transactions to commit simultaneously.
The value of
innodb_commit_concurrencycannot be changed at runtime from zero to nonzero or vice versa. The value can be changed from one nonzero value to another. -
Command-Line Format --innodb_concurrency_tickets=#Option-File Format innodb_concurrency_ticketsSystem Variable Name innodb_concurrency_ticketsVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 500Range 1 .. 4294967295Determines the number of threads that can enter
InnoDBconcurrently. A thread is placed in a queue when it tries to enterInnoDBif the number of threads has already reached the concurrency limit. When a thread is permitted to enterInnoDB, it is given a number of “free tickets” equal to the value ofinnodb_concurrency_tickets, and the thread can enter and leaveInnoDBfreely until it has used up its tickets. After that point, the thread again becomes subject to the concurrency check (and possible queuing) the next time it tries to enterInnoDB. The default value is 500. -
Command-Line Format --innodb_data_file_path=nameOption-File Format innodb_data_file_pathSystem Variable Name innodb_data_file_pathVariable Scope Global Dynamic Variable No Permitted Values Type stringDefault ibdata1:10M:autoextendThe paths to individual
InnoDBdata files and their sizes. The full directory path to each data file is formed by concatenatinginnodb_data_home_dirto each path specified here. The file sizes are specified KB, MB or GB (1024MB) by appendingK,MorGto the size value. If specifying data file size in kilobytes (KB), do so in multiples of 1024. Otherwise, KB values are rounded off to nearest megabyte (MB) boundary. The sum of the sizes of the files must be at least slightly larger than 10MB. If you do not specifyinnodb_data_file_path, the default behavior is to create a single auto-extending data file, slightly larger than 10MB, namedibdata1. The size limit of individual files is determined by your operating system. You can set the file size to more than 4GB on those operating systems that support big files. You can alsouse raw disk partitions as data files. For detailed information on configuringInnoDBtablespace files, see Section 14.6, “InnoDBConfiguration”. -
Command-Line Format --innodb_data_home_dir=pathOption-File Format innodb_data_home_dirSystem Variable Name innodb_data_home_dirVariable Scope Global Dynamic Variable No Permitted Values Type directory nameThe common part of the directory path for all
InnoDBdata files in the system tablespace. This setting does not affect the location of file-per-table tablespaces wheninnodb_file_per_tableis enabled. The default value is the MySQL data directory. If you specify the value as an empty string, you can use absolute file paths ininnodb_data_file_path. -
Command-Line Format --innodb-doublewriteOption-File Format innodb_doublewriteSystem Variable Name innodb_doublewriteVariable Scope Global Dynamic Variable No Permitted Values Type booleanIf this variable is enabled (the default),
InnoDBstores all data twice, first to thedoublewrite buffer, and then to the actual data files. This variable can be turned off with--skip-innodb_doublewritefor benchmarks or cases when top performance is needed rather than concern for data integrity or possible failures. -
Command-Line Format --innodb_fast_shutdown[=#]Option-File Format innodb_fast_shutdownSystem Variable Name innodb_fast_shutdownVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 1Valid Values 012The
InnoDBshutdown mode. If the value is 0,InnoDBdoes a slow shutdown, a full purge and an insert buffer merge before shutting down. If the value is 1 (the default),InnoDBskips these operations at shutdown, a process known as afast shutdown. If the value is 2,InnoDBflushes its logs and shuts down cold, as if MySQL had crashed; no committed transactions are lost, but thecrash recovery operation makes the next startup take longer.The slow shutdown can take minutes, or even hours in extreme cases where substantial amounts of data are still buffered. Use the slow shutdown technique before upgrading or downgrading between MySQL major releases, so that all data files are fully prepared in case the upgrade process updates the file format.
Use
innodb_fast_shutdown=2in emergency or troubleshooting situations, to get the absolute fastest shutdown if data is at risk of corruption. -
Command-Line Format --innodb_file_format=#Option-File Format innodb_file_formatSystem Variable Name innodb_file_formatVariable Scope Global Dynamic Variable Yes Permitted Values (<= 5.5.6) Type stringDefault BarracudaValid Values AntelopeBarracudaPermitted Values (>= 5.5.7) Type stringDefault AntelopeValid Values AntelopeBarracudaThe file format to use for new
InnoDBtables. Currently,AntelopeandBarracudaare supported. This applies only for tables that have their owntablespace, so for it to have an effect,innodb_file_per_tablemust be enabled. The Barracuda file format is required for certain InnoDB features such as table compression.Be aware that
ALTER TABLEoperations that recreateInnoDBtables (ALTER OFFLINE) will use the currentinnodb_file_formatsetting (the conditions outlined above still apply). -
Command-Line Format --innodb_file_format_check=#Option-File Format innodb_file_format_checkSystem Variable Name innodb_file_format_checkVariable Scope Global Dynamic Variable No Permitted Values Type stringDefault AntelopePermitted Values (>= 5.5.1) Type stringDefault BarracudaPermitted Values (>= 5.5.5) Type booleanDefault ONAs of MySQL 5.5.5, this variable can be set to 1 or 0 at server startup to enable or disable whether
InnoDBchecks the file format tag in the system tablespace (for example,AntelopeorBarracuda). If the tag is checked and is higher than that supported by the current version ofInnoDB, an error occurs andInnoDBdoes not start. If the tag is not higher,InnoDBsets the value ofinnodb_file_format_maxto the file format tag.Before MySQL 5.5.5, this variable can be set to 1 or 0 at server startup to enable or disable whether
InnoDBchecks the file format tag in the shared tablespace. If the tag is checked and is higher than that supported by the current version ofInnoDB, an error occurs andInnoDBdoes not start. If the tag is not higher,InnoDBsets the value ofinnodb_file_format_checkto the file format tag, which is the value seen at runtime.NoteDespite the default value sometimes being displayed as
ONorOFF, always use the numeric values 1 or 0 to turn this option on or off in your configuration file or command line. -
Introduced 5.5.5 Command-Line Format --innodb_file_format_max=#Option-File Format innodb_file_format_maxSystem Variable Name innodb_file_format_maxVariable Scope Global Dynamic Variable Yes Permitted Values Type stringDefault AntelopeValid Values AntelopeBarracudaAt server startup,
InnoDBsets the value of this variable to thefile format tag in the system tablespace (for example,AntelopeorBarracuda). If the server creates or opens a table with a “higher” file format, it sets the value ofinnodb_file_format_maxto that format.This variable was added in MySQL 5.5.5.
-
Command-Line Format --innodb_file_per_tableOption-File Format innodb_file_per_tableSystem Variable Name innodb_file_per_tableVariable Scope Global Dynamic Variable Yes Permitted Values (<= 5.5.6) Type booleanDefault ONPermitted Values (>= 5.5.7) Type booleanDefault OFFWhen
innodb_file_per_tableis disabled,InnoDBstores the data for all tables and indexes in the ibdata files that make up the system tablespace. This setting reduces the performance overhead of filesystem operations for operations such asDROP TABLEorTRUNCATE TABLE. It is most appropriate for a server environment where entire storage devices are devoted to MySQL data. Because the system tablespace never shrinks, and is shared across all databases in aninstance, avoid loading huge amounts of temporary data on a space-constrained system wheninnodb_file_per_table=OFF. Set up a separate instance in such cases, so that you can drop the entire instance to reclaim the space.When
innodb_file_per_tableis enabled,InnoDBstores data and indexes for each newly created table in a separate.ibdfile, rather than in the system tablespace. The storage for theseInnoDBtables is reclaimed when the tables are dropped or truncated. This setting enables several otherInnoDBfeatures, such as table compression. See Section 14.8.2, “InnoDB File-Per-Table Mode” for details about such features as well as advantages and disadvantages of using file-per-table tablespaces.Be aware that enabling
innodb_file_per_tablealso means that anALTER TABLEoperation will moveInnoDBtable from the system tablespace to an individual.ibdfile in cases whereALTER TABLErecreates the table (ALTER OFFLINE).In MySQL 5.5 and higher, the configuration parameter
innodb_file_per_tableis dynamic, and can be setONorOFFusingSET GLOBAL. Previously, the only way to set this parameter was in the MySQLconfiguration file (my.cnformy.ini), and changing it required shutting down and restarting the server.Dynamically changing the value of this parameter requires the
SUPERprivilege and immediately affects the operation of all connections. -
innodb_flush_log_at_trx_commitCommand-Line Format --innodb_flush_log_at_trx_commit[=#]Option-File Format innodb_flush_log_at_trx_commitSystem Variable Name innodb_flush_log_at_trx_commitVariable Scope Global Dynamic Variable Yes Permitted Values Type enumerationDefault 1Valid Values 012Controls the balance between strict ACID compliance for commit operations, and higher performance that is possible when commit-related I/O operations are rearranged and done in batches. You can achieve better performance by changing the default value, but then you can lose up to one second worth oftransactions in a crash.
-
The default value of 1 is required for full ACID compliance. With this value, thelog buffer is written out to the log file at each transaction commit and the flush to disk operation is performed on the log file.
-
With a value of 0, any mysqld process crash can erase the last second of transactions. The log buffer is written out to the log file once per second and the flush to disk operation is performed on the log file, but nothing is done at a transaction commit.
-
With a value of 2, an operating system crash or a power outage can erase the last second of commit records. The log buffer is written out to the file at each commit, but the flush to disk operation is not performed on it. However, the flushing on the log file takes place once per second also when the value is 2. Note that the once-per-second flushing is not 100% guaranteed to happen every second, due to process scheduling issues.
-
InnoDB's crash recovery works regardless of the value. Transactions are either applied entirely or erased entirely.
For the greatest possible durability and consistency in a replication setup using
InnoDBwith transactions, useinnodb_flush_log_at_trx_commit=1andsync_binlog=1in your master servermy.cnffile.CautionMany operating systems and some disk hardware fool the flush-to-disk operation. They may tellmysqld that the flush has taken place, even though it has not. Then the durability of transactions is not guaranteed even with the setting 1, and in the worst case a power outage can even corrupt
InnoDBdata. Using a battery-backed disk cache in the SCSI disk controller or in the disk itself speeds up file flushes, and makes the operation safer. You can also try using the Unix commandhdparm to disable the caching of disk writes in hardware caches, or use some other command specific to the hardware vendor. -
-
Command-Line Format --innodb_flush_method=nameOption-File Format innodb_flush_methodSystem Variable Name innodb_flush_methodVariable Scope Global Dynamic Variable No Permitted Values Type (Linux) stringDefault fdatasyncValid Values fdatasyncO_DSYNCO_DIRECTPermitted Values Type (HP-UX) stringDefault fdatasyncValid Values fdatasyncO_DSYNCO_DIRECTPermitted Values Type (Solaris) stringDefault fdatasyncValid Values fdatasyncO_DSYNCO_DIRECTControls the system calls used to flush data to the
InnoDBdata files and log files, which can influence I/O throughput. This variable is relevant only for Unix and Linux systems. On Windows systems, the flush method is alwaysasync_unbufferedand cannot be changed.By default,
InnoDBuses thefsync()system call to flush both the data and log files. Ifinnodb_flush_methodoption is set toO_DSYNC,InnoDBusesO_SYNCto open and flush the log files, andfsync()to flush the data files. IfO_DIRECTis specified (available on some GNU/Linux versions, FreeBSD, and Solaris),InnoDBusesO_DIRECT(ordirectio()on Solaris) to open the data files, and usesfsync()to flush both the data and log files. Note thatInnoDBusesfsync()instead offdatasync(), and it does not useO_DSYNCby default because there have been problems with it on many varieties of Unix.Depending on hardware configuration, setting
innodb_flush_methodtoO_DIRECTcan either have either a positive or negative effect on performance. Benchmark your particular configuration to decide which setting to use. The mix of read and write operations in your workload can also affect which setting performs better for you. For example, on a system with a hardware RAID controller and battery-backed write cache,O_DIRECTcan help to avoid double buffering between theInnoDBbuffer pool and the operating system's filesystem cache. On some systems whereInnoDBdata and log files are located on a SAN, the default value orO_DSYNCmight be faster for a read-heavy workload with mostlySELECTstatements. Always test this parameter with the same type of hardware and workload that reflects your production environment. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”.Formerly, a value of
fdatasyncalso specified the default behavior. This value was removed, due to confusion that a value offdatasynccausedfsync()system calls rather thanfdatasync()for flushing. To obtain the default value now, do not set any value forinnodb_flush_methodat startup. -
Introduced 5.5.18 Command-Line Format --innodb_force_load_corruptedOption-File Format innodb_force_load_corruptedSystem Variable Name innodb_force_load_corruptedVariable Scope Global Dynamic Variable No Permitted Values Type booleanDefault OFFLets InnoDB load tables at startup that are marked as corrupted. Use only during troubleshooting, to recover data that is otherwise inaccessible. When troubleshooting is complete, turn this setting back off and restart the server.
-
Command-Line Format --innodb_force_recovery=#Option-File Format innodb_force_recoverySystem Variable Name innodb_force_recoveryVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 0Range 0 .. 6The crash recovery mode, typically only changed in serious troubleshooting situations. Possible values are from 0 to 6. The meanings of these values are described inSection 14.21.2, “Starting
InnoDBon a Corrupted Database”.WarningOnly set this variable greater than 0 in an emergency situation, to dump your tables from a corrupt database. As a safety measure,
InnoDBprevents any changes to its data when this variable is greater than 0. This restriction also prohibits some queries that useWHEREorORDER BYclauses, because high values can prevent queries from using indexes, to guard against possible corrupt index data. -
Command-Line Format --innodb_io_capacity=#Option-File Format innodb_io_capacitySystem Variable Name innodb_io_capacityVariable Scope Global Dynamic Variable Yes Permitted Values Platform Bit Size 32Type numericDefault 200Range 100 .. 2**32-1Permitted Values Platform Bit Size 64Type numericDefault 200Range 100 .. 2**64-1The
innodb_io_capacityparameter sets an upper limit on the I/O activity performed by theInnoDBbackground tasks, such as flushing pages from the buffer pool and merging data from the insert buffer. The default value is 200. For busy systems capable of higher I/O rates, you can set a higher value at server startup, to help the server handle the background maintenance work associated with a high rate of row changes. For systems with individual 5400 RPM or 7200 RPM drives, you might lower the value to the former default of100.The
innodb_io_capacitylimit is a total limit for all buffer pool instances. When dirty pages are flushed, theinnodb_io_capacitylimit is divided equally among buffer pool instances.This parameter should be set to approximately the number of I/O operations that the system can perform per second. Ideally, keep this setting as low as practical, but not so low that these background activities fall behind. If the value is too high, data is removed from the buffer pool and insert buffer too quickly to provide significant benefit from the caching.
The value represents an estimated proportion of the I/O operations per second (IOPS) available to older-generation disk drives that could perform about 100 IOPS. The current default of 200 reflects that modern storage devices are capable of much higher I/O rates.
In general, you can increase the value as a function of the number of drives used for
InnoDBI/O, particularly fast drives capable of high numbers of IOPS. For example, systems that use multiple disks or solid-state disks forInnoDBare likely to benefit from the ability to control this parameter.Although you can specify a very high number, in practice such large values have little if any benefit; for example, a value of one million would be considered very high.
You can set the
innodb_io_capacityvalue to any number 100 or greater, and the default value is200. You can set the value of this parameter in the MySQL option file (my.cnformy.ini) or change it dynamically with theSET GLOBALcommand, which requires theSUPERprivilege.See Section 14.16.9, “Configuring the
InnoDBMaster Thread I/O Rate” for more guidelines about this option. For general information about InnoDB I/O performance, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”. -
Introduced 5.5.14 Command-Line Format --innodb_large_prefixOption-File Format innodb_large_prefixSystem Variable Name innodb_large_prefixVariable Scope Global Dynamic Variable Yes Permitted Values Type booleanDefault OFFEnable this option to allow index key prefixes longer than 767 bytes (up to 3072 bytes), for
InnoDBtables that use theDYNAMICandCOMPRESSEDrow formats. (Creating such tables also requires the option valuesinnodb_file_format=barracudaandinnodb_file_per_table=true.) See Section 14.9.7, “Limits onInnoDBTables” for the relevant maximums associated with index key prefixes under various settings.For tables using the
REDUNDANTandCOMPACTrow formats, this option does not affect the allowed key prefix length. It does introduce a new error possibility. When this setting is enabled, attempting to create an index prefix with a key length greater than 3072 for aREDUNDANTorCOMPACTtable causes anER_INDEX_COLUMN_TOO_LONGerror. -
Command-Line Format --innodb_lock_wait_timeout=#Option-File Format innodb_lock_wait_timeoutSystem Variable Name innodb_lock_wait_timeoutVariable Scope Global, Session Dynamic Variable Yes Permitted Values Type numericDefault 50Range 1 .. 1073741824The length of time in seconds an
InnoDBtransaction waits for a row lock before giving up. The default value is 50 seconds. A transaction that tries to access a row that is locked by anotherInnoDBtransaction waits at most this many seconds for write access to the row before issuing the following error:ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction
When a lock wait timeout occurs, the current statement is rolled back (not the entire transaction). To have the entire transaction roll back, start the server with the
--innodb_rollback_on_timeoutoption. See also Section 14.21.4, “InnoDBError Handling”.You might decrease this value for highly interactive applications or OLTP systems, to display user feedback quickly or put the update into a queue for processing later. You might increase this value for long-running back-end operations, such as a transform step in a data warehouse that waits for other large insert or update operations to finish.
innodb_lock_wait_timeoutapplies toInnoDBrow locks only. A MySQL table lock does not happen insideInnoDBand this timeout does not apply to waits for table locks.The lock wait timeout value does not apply to deadlocks, because
InnoDBdetects them immediately and rolls back one of the deadlocked transactions.As of MySQL 5.5,
innodb_lock_wait_timeoutcan be set at runtime with theSET GLOBALorSET SESSIONstatement. Changing theGLOBALsetting requires theSUPERprivilege and affects the operation of all clients that subsequently connect. Any client can change theSESSIONsetting forinnodb_lock_wait_timeout, which affects only that client. -
innodb_locks_unsafe_for_binlogCommand-Line Format --innodb_locks_unsafe_for_binlogOption-File Format innodb_locks_unsafe_for_binlogSystem Variable Name innodb_locks_unsafe_for_binlogVariable Scope Global Dynamic Variable No Permitted Values Type booleanDefault OFFThis variable affects how
InnoDBuses gap locking for searches and index scans. Normally,InnoDBuses an algorithm called next-key locking that combines index-row locking with gap locking.InnoDBperforms row-level locking in such a way that when it searches or scans a table index, it sets shared or exclusive locks on the index records it encounters. Thus, the row-level locks are actually index-record locks. In addition, a next-key lock on an index record also affects the “gap” before that index record. That is, a next-key lock is an index-record lock plus a gap lock on the gap preceding the index record. If one session has a shared or exclusive lock on recordRin an index, another session cannot insert a new index record in the gap immediately beforeRin the index order. See Section 14.5.6, “InnoDBRecord, Gap, and Next-Key Locks”.By default, the value of
innodb_locks_unsafe_for_binlogis 0 (disabled), which means that gap locking is enabled:InnoDBuses next-key locks for searches and index scans. To enable the variable, set it to 1. This causes gap locking to be disabled:InnoDBuses only index-record locks for searches and index scans.Enabling
innodb_locks_unsafe_for_binlogdoes not disable the use of gap locking for foreign-key constraint checking or duplicate-key checking.The effect of enabling
innodb_locks_unsafe_for_binlogis similar to but not identical to setting the transaction isolation level toREAD COMMITTED:-
Enabling
innodb_locks_unsafe_for_binlogis a global setting and affects all sessions, whereas the isolation level can be set globally for all sessions, or individually per session. -
innodb_locks_unsafe_for_binlogcan be set only at server startup, whereas the isolation level can be set at startup or changed at runtime.
READ COMMITTEDtherefore offers finer and more flexible control thaninnodb_locks_unsafe_for_binlog. For additional details about the effect of isolation level on gap locking, seeSection 13.3.6, “SET TRANSACTIONSyntax”.Enabling
innodb_locks_unsafe_for_binlogmay cause phantom problems because other sessions can insert new rows into the gaps when gap locking is disabled. Suppose that there is an index on theidcolumn of thechildtable and that you want to read and lock all rows from the table having an identifier value larger than 100, with the intention of updating some column in the selected rows later:SELECT * FROM child WHERE id > 100 FOR UPDATE;
The query scans the index starting from the first record where
idis greater than 100. If the locks set on the index records in that range do not lock out inserts made in the gaps, another session can insert a new row into the table. Consequently, if you were to execute the sameSELECTagain within the same transaction, you would see a new row in the result set returned by the query. This also means that if new items are added to the database,InnoDBdoes not guarantee serializability. Therefore, ifinnodb_locks_unsafe_for_binlogis enabled,InnoDBguarantees at most an isolation level ofREAD COMMITTED. (Conflict serializability is still guaranteed.) For additional information about phantoms, seeSection 14.5.7, “Avoiding the Phantom Problem Using Next-Key Locking”.Enabling
innodb_locks_unsafe_for_binloghas additional effects:-
For
UPDATEorDELETEstatements,InnoDBholds locks only for rows that it updates or deletes. Record locks for nonmatching rows are released after MySQL has evaluated theWHEREcondition. This greatly reduces the probability of deadlocks, but they can still happen. -
For
UPDATEstatements, if a row is already locked,InnoDBperforms a “semi-consistent” read, returning the latest committed version to MySQL so that MySQL can determine whether the row matches theWHEREcondition of theUPDATE. If the row matches (must be updated), MySQL reads the row again and this timeInnoDBeither locks it or waits for a lock on it.
Consider the following example, beginning with this table:
CREATE TABLE t (a INT NOT NULL, b INT) ENGINE = InnoDB; INSERT INTO t VALUES (1,2),(2,3),(3,2),(4,3),(5,2); COMMIT;
In this case, table has no indexes, so searches and index scans use the hidden clustered index for record locking (seeSection 14.5.13.2, “Clustered and Secondary Indexes”).
Suppose that one client performs an
UPDATEusing these statements:SET autocommit = 0; UPDATE t SET b = 5 WHERE b = 3;
Suppose also that a second client performs an
UPDATEby executing these statements following those of the first client:SET autocommit = 0; UPDATE t SET b = 4 WHERE b = 2;
As
InnoDBexecutes eachUPDATE, it first acquires an exclusive lock for each row, and then determines whether to modify it. IfInnoDBdoes not modify the row andinnodb_locks_unsafe_for_binlogis enabled, it releases the lock. Otherwise,InnoDBretains the lock until the end of the transaction. This affects transaction processing as follows.If
innodb_locks_unsafe_for_binlogis disabled, the firstUPDATEacquires x-locks and does not release any of them:x-lock(1,2); retain x-lock x-lock(2,3); update(2,3) to (2,5); retain x-lock x-lock(3,2); retain x-lock x-lock(4,3); update(4,3) to (4,5); retain x-lock x-lock(5,2); retain x-lock
The second
UPDATEblocks as soon as it tries to acquire any locks (because first update has retained locks on all rows), and does not proceed until the firstUPDATEcommits or rolls back:x-lock(1,2); block and wait for first UPDATE to commit or roll back
If
innodb_locks_unsafe_for_binlogis enabled, the firstUPDATEacquires x-locks and releases those for rows that it does not modify:x-lock(1,2); unlock(1,2) x-lock(2,3); update(2,3) to (2,5); retain x-lock x-lock(3,2); unlock(3,2) x-lock(4,3); update(4,3) to (4,5); retain x-lock x-lock(5,2); unlock(5,2)
For the second
UPDATE,InnoDBdoes a“semi-consistent” read, returning the latest committed version of each row to MySQL so that MySQL can determine whether the row matches theWHEREcondition of theUPDATE:x-lock(1,2); update(1,2) to (1,4); retain x-lock x-lock(2,3); unlock(2,3) x-lock(3,2); update(3,2) to (3,4); retain x-lock x-lock(4,3); unlock(4,3) x-lock(5,2); update(5,2) to (5,4); retain x-lock
-
-
Command-Line Format --innodb_log_buffer_size=#Option-File Format innodb_log_buffer_sizeSystem Variable Name innodb_log_buffer_sizeVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 8388608Range 262144 .. 4294967295The size in bytes of the buffer that
InnoDBuses to write to thelog files on disk. The default value is 8MB. A large log buffer enables large transactions to run without a need to write the log to disk before the transactionscommit. Thus, if you have transactions that update, insert, or delete many rows, making the log buffer larger saves disk I/O. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”. -
Command-Line Format --innodb_log_file_size=#Option-File Format innodb_log_file_sizeSystem Variable Name innodb_log_file_sizeVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 5242880Range 1048576 .. 4GB / innodb_log_files_in_groupThe size in bytes of each log file in a log group. The combined size of log files (
innodb_log_file_size*innodb_log_files_in_group) cannot exceed a maximum value that is slightly less than 4GB. A pair of 2047 MB log files, for example, would allow you to approach the range limit but not exceed it. The default value is 5MB. Sensible values range from 1MB to 1/N-th of the size of the buffer pool, whereNis the number of log files in the group. The larger the value, the less checkpoint flush activity is needed in the buffer pool, saving disk I/O. Larger log files also makecrash recovery slower, although improvements to recovery performance in MySQL 5.5 and higher make the log file size less of a consideration. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”. -
Command-Line Format --innodb_log_files_in_group=#Option-File Format innodb_log_files_in_groupSystem Variable Name innodb_log_files_in_groupVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 2Range 2 .. 100The number of log files in the log group.
InnoDBwrites to the files in a circular fashion. The default (and recommended) value is 2. The location of these files is specified byinnodb_log_group_home_dir. -
Command-Line Format --innodb_log_group_home_dir=pathOption-File Format innodb_log_group_home_dirSystem Variable Name innodb_log_group_home_dirVariable Scope Global Dynamic Variable No Permitted Values Type directory nameThe directory path to the
InnoDBredo log files, whose number is specified byinnodb_log_files_in_group. If you do not specify anyInnoDBlog variables, the default is to create two files namedib_logfile0andib_logfile1in the MySQL data directory. Their size is given by the size of theinnodb_log_file_sizesystem variable. -
Command-Line Format --innodb_max_dirty_pages_pct=#Option-File Format innodb_max_dirty_pages_pctSystem Variable Name innodb_max_dirty_pages_pctVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 75Range 0 .. 99InnoDBtries to flush data from the buffer pool so that the percentage of dirty pages does not exceed this value. Specify an integer in the range from 0 to 99. The default value is 75.For additional information about this variable, see Section 14.16.2.2, “Configuring the Rate of
InnoDBBuffer Pool Flushing”. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”. -
Command-Line Format --innodb_max_purge_lag=#Option-File Format innodb_max_purge_lagSystem Variable Name innodb_max_purge_lagVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 0Range 0 .. 4294967295This variable controls how to delay
INSERT,UPDATE, andDELETEoperations when purge operations are lagging (see Section 14.5.12, “InnoDBMulti-Versioning”). The default value is 0 (no delays).The
InnoDBtransaction system maintains a list of transactions that have index records delete-marked byUPDATEorDELETEoperations. The length of this list represents thepurge_lagvalue. Whenpurge_lagexceedsinnodb_max_purge_lag, eachINSERT,UPDATE, andDELETEoperation is delayed by ((purge_lag/innodb_max_purge_lag)×10)–5 milliseconds. The delay is computed in the beginning of a purge batch, every ten seconds. The operations are not delayed if purge cannot run because of an oldconsistent read view that could see the rows to be purged.A typical setting for a problematic workload might be 1 million, assuming that transactions are small, only 100 bytes in size, and it is permissible to have 100MB of unpurged
InnoDBtable rows.The lag value is displayed as the history list length in the
TRANSACTIONSsection of InnoDB Monitor output. For example, if the output includes the following lines, the lag value is 20:------------ TRANSACTIONS ------------ Trx id counter 0 290328385 Purge done for trx's n:o < 0 290315608 undo n:o < 0 17 History list length 20
For general I/O tuning advice, see Section 8.5.7, “Optimizing
InnoDBDisk I/O”. -
Has no effect.
-
Command-Line Format --innodb_old_blocks_pct=#Option-File Format innodb_old_blocks_pctSystem Variable Name innodb_old_blocks_pctVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 37Range 5 .. 95Specifies the approximate percentage of the
InnoDBbuffer pool used for the old block sublist. The range of values is 5 to 95. The default value is 37 (that is, 3/8 of the pool). SeeSection 14.16.2.3, “Making the Buffer Pool Scan Resistant” for more information. SeeSection 8.9.1, “TheInnoDBBuffer Pool” for information about buffer pool management, such as theLRU algorithm and eviction policies. -
Command-Line Format --innodb_old_blocks_time=#Option-File Format innodb_old_blocks_timeSystem Variable Name innodb_old_blocks_timeVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 0Range 0 .. 2**32-1Non-zero values protect against the buffer pool being filled up by data that is referenced only for a brief period, such as during afull table scan. Increasing this value offers more protection against full table scans interfering with data cached in the buffer pool.
Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before it can be moved to the new sublist. If the value is 0, a block inserted into the old sublist moves immediately to the new sublist the first time it is accessed, no matter how soon after insertion the access occurs. If the value is greater than 0, blocks remain in the old sublist until an access occurs at least that many ms after the first access. For example, a value of 1000 causes blocks to stay in the old sublist for 1 second after the first access before they become eligible to move to the new sublist.
This variable is often used in combination with
innodb_old_blocks_pct. See Section 14.16.2.3, “Making the Buffer Pool Scan Resistant” for more information. SeeSection 8.9.1, “TheInnoDBBuffer Pool” for information about buffer pool management, such as theLRU algorithm and eviction policies. -
Command-Line Format --innodb_open_files=#Option-File Format innodb_open_filesSystem Variable Name innodb_open_filesVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 300Range 10 .. 4294967295This variable is relevant only if you use multiple
InnoDBtablespaces. It specifies the maximum number of.ibdfiles that MySQL can keep open at one time. The minimum value is 10. The default value is 300.The file descriptors used for
.ibdfiles are forInnoDBtables only. They are independent of those specified by the--open-files-limitserver option, and do not affect the operation of the table cache. -
Introduced 5.5.30 Command-Line Format --innodb_print_all_deadlocks=#Option-File Format innodb_print_all_deadlocksSystem Variable Name innodb_print_all_deadlocksVariable Scope Global Dynamic Variable Yes Permitted Values Type booleanDefault OFFWhen this option is enabled, information about all deadlocks in
InnoDBuser transactions is recorded in themysqlderror log. Otherwise, you see information about only the last deadlock, using theSHOW ENGINE INNODB STATUScommand. An occasionalInnoDBdeadlock is not necessarily an issue, becauseInnoDBdetects the condition immediately, and rolls back one of the transactions automatically. You might use this option to troubleshoot why deadlocks are happening if an application does not have appropriate error-handling logic to detect the rollback and retry its operation. A large number of deadlocks might indicate the need to restructure transactions that issueDML orSELECT ... FOR UPDATEstatements for multiple tables, so that each transaction accesses the tables in the same order, thus avoiding the deadlock condition. -
Introduced 5.5.4 Command-Line Format --innodb_purge_batch_size=#Option-File Format innodb_purge_batch_sizeSystem Variable Name innodb_purge_batch_sizeVariable Scope Global Dynamic Variable Yes Permitted Values (>= 5.5.4) Type numericDefault 20Range 1 .. 5000The granularity of changes, expressed in units of redo log records, that trigger a purge operation, flushing the changed buffer pool blocks to disk. This option is intended for tuning performance in combination with the setting
innodb_purge_threads=, and typical users do not need to modify it.n -
Introduced 5.5.4 Command-Line Format --innodb_purge_threads=#Option-File Format innodb_purge_threadsSystem Variable Name innodb_purge_threadsVariable Scope Global Dynamic Variable No Permitted Values (>= 5.5.4) Type numericDefault 0Range 0 .. 1The number of background threads devoted to the InnoDB purge operation. Currently, can only be 0 (the default) or 1. The default value of 0 signifies that the purge operation is performed as part of themaster thread. Running the purge operation in its own thread can reduce internal contention within InnoDB, improving scalability. Currently, the performance gain might be minimal because the background thread might encounter different kinds of contention than before. This feature primarily lays the groundwork for future performance work.
-
Introduced 5.5.16 Command-Line Format --innodb_random_read_ahead=#Option-File Format innodb_random_read_aheadSystem Variable Name innodb_random_read_aheadVariable Scope Global Dynamic Variable Yes Permitted Values Type booleanDefault OFFEnables the random read-ahead technique for optimizing
InnoDBI/O. This is a setting that was originally on by default, then was removed in MySQL 5.5, and now is available but turned off by default. SeeSection 14.16.2.1, “ConfiguringInnoDBBuffer Pool Prefetching (Read-Ahead)” for details about the performance considerations for the different types of read-ahead requests. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”. -
Command-Line Format --innodb_read_ahead_threshold=#Option-File Format innodb_read_ahead_thresholdSystem Variable Name innodb_read_ahead_thresholdVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 56Range 0 .. 64Controls the sensitivity of linear read-ahead that
InnoDBuses to prefetch pages into thebuffer pool. IfInnoDBreads at leastinnodb_read_ahead_thresholdpages sequentially from an extent (64 pages), it initiates an asynchronous read for the entire following extent. The permissible range of values is 0 to 64. The default is 56:InnoDBmust read at least 56 pages sequentially from an extent to initiate an asynchronous read for the following extent.Knowing how many pages are read through this read-ahead mechanism, and how many of them are evicted from the buffer pool without ever being accessed, can be useful to help fine-tune the
innodb_read_ahead_thresholdparameter. As of MySQL 5.5,SHOW ENGINE INNODB STATUSoutput displays counter information from theInnodb_buffer_pool_read_aheadandInnodb_buffer_pool_read_ahead_evictedglobal status variables. These variables indicate the number of pages brought into thebuffer pool by read-ahead requests, and the number of such pages evicted from the buffer pool without ever being accessed respectively. These counters provide global values since the last server restart.SHOW ENGINE INNODB STATUSalso shows the rate at which the read-ahead pages are read in and the rate at which such pages are evicted without being accessed. The per-second averages are based on the statistics collected since the last invocation ofSHOW ENGINE INNODB STATUSand are displayed in theBUFFER POOL AND MEMORYsection of the output.See Section 14.16.2.1, “Configuring
InnoDBBuffer Pool Prefetching (Read-Ahead)” for more information. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”. -
Command-Line Format --innodb_read_io_threads=#Option-File Format innodb_read_io_threadsSystem Variable Name innodb_read_io_threadsVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 4Range 1 .. 64The number of I/O threads for read operations in
InnoDB. The default value is 4. Its counterpart for write threads isinnodb_write_io_threads. See Section 14.16.7, “Configuring the Number of BackgroundInnoDBI/O Threads” for more information. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”.NoteOn Linux systems, running multiple MySQL servers (typically more than 12) with default settings for
innodb_read_io_threads,innodb_write_io_threads, and the Linuxaio-max-nrsetting can exceed system limits. Ideally, increase theaio-max-nrsetting; as a workaround, you might reduce the settings for one or both of the MySQL configuration options. -
Command-Line Format --innodb_replication_delay=#Option-File Format innodb_replication_delaySystem Variable Name innodb_replication_delayVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 0Range 0 .. 4294967295The replication thread delay (in ms) on a slave server if
innodb_thread_concurrencyis reached. -
Command-Line Format --innodb_rollback_on_timeoutOption-File Format innodb_rollback_on_timeoutSystem Variable Name innodb_rollback_on_timeoutVariable Scope Global Dynamic Variable No Permitted Values Type booleanDefault OFFIn MySQL 5.5,
InnoDBrolls back only the last statement on a transaction timeout by default. If--innodb_rollback_on_timeoutis specified, a transaction timeout causesInnoDBto abort and roll back the entire transaction (the same behavior as in MySQL 4.1). -
Introduced 5.5.11 Command-Line Format --innodb_rollback_segments=#Option-File Format innodb_rollback_segmentsSystem Variable Name innodb_rollback_segmentsVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 128Range 1 .. 128Defines how many of the rollback segments in the system tablespace that InnoDB uses within a transaction. You might reduce this value from its default of 128 if a smaller number of rollback segments performs better for your workload.
-
Command-Line Format --innodb_spin_wait_delay=#Option-File Format innodb_spin_wait_delaySystem Variable Name innodb_spin_wait_delayVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 6Range 0 .. 4294967295The maximum delay between polls for a spin lock. The low-level implementation of this mechanism varies depending on the combination of hardware and operating system, so the delay does not correspond to a fixed time interval. The default value is 6. SeeSection 14.16.11, “Configuring Spin Lock Polling” for more information.
-
Introduced 5.5.10 Command-Line Format --innodb_stats_method=nameOption-File Format innodb_stats_methodSystem Variable Name innodb_stats_methodVariable Scope Global Dynamic Variable Yes Permitted Values Type enumerationDefault nulls_equalValid Values nulls_equalnulls_unequalnulls_ignoredHow the server treats
NULLvalues when collectingstatistics about the distribution of index values forInnoDBtables. This variable has three possible values,nulls_equal,nulls_unequal, andnulls_ignored. Fornulls_equal, allNULLindex values are considered equal and form a single value group that has a size equal to the number ofNULLvalues. Fornulls_unequal,NULLvalues are considered unequal, and eachNULLforms a distinct value group of size 1. Fornulls_ignored,NULLvalues are ignored.The method that is used for generating table statistics influences how the optimizer chooses indexes for query execution, as described inSection 8.3.7, “
InnoDBandMyISAMIndex Statistics Collection”. -
Introduced 5.5.4 Command-Line Format --innodb_stats_on_metadataOption-File Format innodb_stats_on_metadataSystem Variable Name innodb_stats_on_metadataVariable Scope Global Dynamic Variable Yes Permitted Values Type booleanDefault ONWhen this variable is enabled (which is the default, as before the variable was created),
InnoDBupdates statistics when metadata statements such asSHOW TABLE STATUSorSHOW INDEXare run, or when accessing theINFORMATION_SCHEMAtablesTABLESorSTATISTICS. (These updates are similar to what happens forANALYZE TABLE.) When disabled,InnoDBdoes not update statistics during these operations. Disabling this variable can improve access speed for schemas that have a large number of tables or indexes. It can also improve the stability ofexecution plans for queries that involveInnoDBtables.To change the setting, issue the statement
SET GLOBAL innodb_stats_on_metadata=, wheremodemodeis eitherONorOFF(or1or0). Changing this setting requires theSUPERprivilege and immediately affects the operation of all connections. -
Command-Line Format --innodb_stats_sample_pages=#Option-File Format innodb_stats_sample_pagesSystem Variable Name innodb_stats_sample_pagesVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 8Range 1 .. 2**64-1The number of index pages to sample for index distribution statistics such as are calculated by
ANALYZE TABLE. The default value is 8. For additional information, seeSection 14.16.15, “Configuring Optimizer Statistics Parameters”.Setting a high value for
innodb_stats_sample_pagescould result in lengthyANALYZE TABLEexecution time. To estimate the number of database pages accessed byANALYZE TABLE, see Section 14.16.16, “EstimatingANALYZE TABLEComplexity forInnoDBTables”. -
Command-Line Format --innodb_strict_mode=#Option-File Format innodb_strict_modeSystem Variable Name innodb_strict_modeVariable Scope Global, Session Dynamic Variable Yes Permitted Values Type booleanDefault OFFWhen
innodb_strict_modeisON,InnoDBreturns errors rather than warnings for certain conditions. The default value isOFF.Strict mode helps guard against ignored typos and syntax errors in SQL, or other unintended consequences of various combinations of operational modes and SQL statements. When
innodb_strict_modeisON,InnoDBraises error conditions in certain cases, rather than issuing a warning and processing the specified statement (perhaps with unintended behavior). This is analogous tosql_modein MySQL, which controls what SQL syntax MySQL accepts, and determines whether it silently ignores errors, or validates input syntax and data values.The
innodb_strict_modesetting affects the handling of syntax errors forCREATE TABLE,ALTER TABLEandCREATE INDEXstatements.innodb_strict_modealso enables a record size check, so that anINSERTorUPDATEnever fails due to the record being too large for the selected page size.Oracle recommends enabling
innodb_strict_modewhen usingROW_FORMATandKEY_BLOCK_SIZEclauses onCREATE TABLE,ALTER TABLE, andCREATE INDEXstatements. Wheninnodb_strict_modeisOFF,InnoDBignores conflicting clauses and creates the table or index, with only a warning in the message log. The resulting table might have different behavior than you intended, such as having no compression when you tried to create a compressed table. Wheninnodb_strict_modeisON, such problems generate an immediate error and the table or index is not created, avoiding a troubleshooting session later.You can turn
innodb_strict_modeONorOFFon the command line when you startmysqld, or in the configuration filemy.cnformy.ini. You can also enable or disableinnodb_strict_modeat runtime with the statementSET [GLOBAL|SESSION] innodb_strict_mode=, wheremodemodeis eitherONorOFF. Changing theGLOBALsetting requires theSUPERprivilege and affects the operation of all clients that subsequently connect. Any client can change theSESSIONsetting forinnodb_strict_mode, and the setting affects only that client. -
Command-Line Format --innodb_support_xaOption-File Format innodb_support_xaSystem Variable Name innodb_support_xaVariable Scope Global, Session Dynamic Variable Yes Permitted Values Type booleanDefault TRUEEnables
InnoDBsupport for two-phase commit in XA transactions, causing an extra disk flush for transaction preparation. This setting is the default. The XA mechanism is used internally and is essential for any server that has its binary log turned on and is accepting changes to its data from more than one thread. If you turn it off, transactions can be written to the binary log in a different order from the one in which the live database is committing them. This can produce different data when the binary log is replayed in disaster recovery or on a replication slave. Do not turn it off on a replication master server unless you have an unusual setup where only one thread is able to change data.For a server that is accepting data changes from only one thread, it is safe and recommended to turn off this option to improve performance for
InnoDBtables. For example, you can turn it off on replication slaves where only the replication SQL thread is changing data.You can also turn off this option if you do not need it for safe binary logging or replication, and you also do not use an external XA transaction manager.
-
Command-Line Format --innodb_sync_spin_loops=#Option-File Format innodb_sync_spin_loopsSystem Variable Name innodb_sync_spin_loopsVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 30Range 0 .. 4294967295The number of times a thread waits for an
InnoDBmutex to be freed before the thread is suspended. The default value is 30. -
Command-Line Format --innodb_table_locksOption-File Format innodb_table_locksSystem Variable Name innodb_table_locksVariable Scope Global, Session Dynamic Variable Yes Permitted Values Type booleanDefault TRUEIf
autocommit = 0,InnoDBhonorsLOCK TABLES; MySQL does not return fromLOCK TABLES ... WRITEuntil all other threads have released all their locks to the table. The default value ofinnodb_table_locksis 1, which means thatLOCK TABLEScauses InnoDB to lock a table internally ifautocommit = 0.As of MySQL 5.5.3,
innodb_table_locks = 0has no effect for tables locked explicitly withLOCK TABLES ... WRITE. It still has an effect for tables locked for read or write byLOCK TABLES ... WRITEimplicitly (for example, through triggers) or byLOCK TABLES ... READ. -
Command-Line Format --innodb_thread_concurrency=#Option-File Format innodb_thread_concurrencySystem Variable Name innodb_thread_concurrencyVariable Scope Global Dynamic Variable Yes Permitted Values Type numericDefault 0Range 0 .. 1000InnoDBtries to keep the number of operating system threads concurrently insideInnoDBless than or equal to the limit given by this variable. Once the number of threads reaches this limit, additional threads are placed into a wait state within a FIFO queue for execution. Threads waiting for locks are not counted in the number of concurrently executing threads.The correct value for this variable is dependent on environment and workload. Try a range of different values to determine what value works for your applications. A recommended value is 2 times the number of CPUs plus the number of disks.
The range of this variable is 0 to 1000. A value of 0 (the default) is interpreted as infinite concurrency (no concurrency checking). Disabling thread concurrency checking enables InnoDB to create as many threads as it needs. A value of 0 also disables the
queries inside InnoDBandqueries in queue countersin theROW OPERATIONSsection ofSHOW ENGINE INNODB STATUSoutput. -
Command-Line Format --innodb_thread_sleep_delay=#Option-File Format innodb_thread_sleep_delaySystem Variable Name innodb_thread_sleep_delayVariable Scope Global Dynamic Variable Yes Permitted Values (<= 5.5.36) Platform Bit Size 32Type numericDefault 10000Range 0 .. 4294967295Permitted Values (<= 5.5.36) Platform Bit Size 64Type numericDefault 10000Range 0 .. 18446744073709551615Permitted Values (>= 5.5.37) Type numericDefault 10000Range 0 .. 1000000How long
InnoDBthreads sleep before joining theInnoDBqueue, in microseconds. The default value is 10,000. A value of 0 disables sleep. -
Introduced 5.5.4 Command-Line Format --innodb_use_native_aio=#Option-File Format innodb_use_native_aioSystem Variable Name innodb_use_native_aioVariable Scope Global Dynamic Variable No Permitted Values Type booleanDefault ONSpecifies whether to use the Linux asynchronous I/O subsystem. This variable applies to Linux systems only, and cannot be changed while the server is running. Normally, you do not need to touch this option, because it is enabled by default.
As of MySQL 5.5, the asynchronous I/O capability that
InnoDBhas on Windows systems is available on Linux systems. (Other Unix-like systems continue to use synchronous I/O calls.) This feature improves the scalability of heavily I/O-bound systems, which typically show many pending reads/writes in the output of the commandSHOW ENGINE INNODB STATUS\G.Running with a large number of
InnoDBI/O threads, and especially running multiple such instances on the same server machine, can exceed capacity limits on Linux systems. In this case, you may receive the following error:EAGAIN: The specified maxevents exceeds the user's limit of available events.
You can typically address this error by writing a higher limit to
/proc/sys/fs/aio-max-nr.However, if a problem with the asynchronous I/O subsystem in the OS prevents
InnoDBfrom starting, you can start the server withinnodb_use_native_aio=0disabled (useinnodb_use_native_aio=0in the option file). This option may also be turned off automatically during startup ifInnoDBdetects a potential problem such as a combination oftmpdirlocation,tmpfsfilesystem, and Linux kernel that does not support AIO ontmpfs.This variable was added in MySQL 5.5.4.
-
Command-Line Format --innodb_use_sys_malloc=#Option-File Format innodb_use_sys_mallocSystem Variable Name innodb_use_sys_mallocVariable Scope Global Dynamic Variable No Permitted Values Type booleanDefault ONWhether
InnoDBuses the operating system memory allocator (ON) or its own (OFF). The default value isON. See Section 14.16.4, “Configuring the Memory Allocator forInnoDB” for more information. -
The
InnoDBversion number. Starting in 5.5.30, the separate numbering forInnoDBis discontinued and this value is the same as for theversionvariable. -
Command-Line Format --innodb_write_io_threads=#Option-File Format innodb_write_io_threadsSystem Variable Name innodb_write_io_threadsVariable Scope Global Dynamic Variable No Permitted Values Type numericDefault 4Range 1 .. 64The number of I/O threads for write operations in
InnoDB. The default value is 4. Its counterpart for read threads isinnodb_read_io_threads. See Section 14.16.7, “Configuring the Number of BackgroundInnoDBI/O Threads” for more information. For general I/O tuning advice, seeSection 8.5.7, “OptimizingInnoDBDisk I/O”.NoteOn Linux systems, running multiple MySQL servers (typically more than 12) with default settings for
innodb_read_io_threads,innodb_write_io_threads, and the Linuxaio-max-nrsetting can exceed system limits. Ideally, increase theaio-max-nrsetting; as a workaround, you might reduce the settings for one or both of the MySQL configuration options.
You should also take into consideration the value of sync_binlog, which controls synchronization of the binary log to disk.
For general I/O tuning advice, see Section 8.5.7, “Optimizing InnoDB Disk I/O”.
91
到【灌水乐园】发言
User Comments
Be careful when being too aggressive with settings like innodb_buffer_pool_size. Although your system might have a lot of RAM installed, a 32-bit Linux operating can't allocate more than 2.2-2.7G* per process.
* This limit varies in different kernels.
I am using innodb_file_per_table to separate the files out so when i delete database, we can get our disk usage back. I go into details in my blog which I hope helps somebody.
http://crazytoon.com/2007/04/03/mysql-ibdata-files-do-not-shrink-on-database-deletion-innodb/
Commentary on Innodb parameters for an 8way machine:
http://krow.livejournal.com/542306.html
Changing innodb_log_file_size can yield strange errors, such as: Incorrect information in file: './db010840/notifications.frm'
This is particularly of importance when performing a file based sync to setup replication. If you have a different (or no) innodb_log_file_size setting at the slave, you will be puzzled for hours (I was).
NOTE: The time to Initialise the innodb buffer pool is roughly proportional to the size of the pool created. On large installations[*] this initialisation time may be significant.
[*] 2009/10 Initialising a 10 GB buffer pool takes 6 seconds, larger configurations may take proportionally longer.
It would have been better if the parameters given in here were with concrete examples. I hope it would be done in the future releases.
I wrote a guide for what to tune in MySQL 5.6 after installation here:
http://www.tocker.ca/2013/09/17/what-to-tune-in-mysql-56-after-installation.html