From: paul.dubois Date: November 5 2009 7:48pm Subject: svn commit - mysqldoc@docsrva: r17480 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0.sav List-Archive: http://lists.mysql.com/commits/89519 Message-Id: <200911051948.nA5Jmqtp030629@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: paul Date: 2009-11-05 20:48:52 +0100 (Thu, 05 Nov 2009) New Revision: 17480 Log: r46182@frost: paul | 2009-11-05 13:10:07 -0500 Restructure list Modified: trunk/refman-4.1/se-innodb-core.xml trunk/refman-5.0/se-innodb-core.xml trunk/refman-5.1/se-innodb-core.xml trunk/refman-5.4/se-innodb-core.xml trunk/refman-5.5/se-innodb-core.xml trunk/refman-6.0.sav/se-innodb-core.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27523 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46179 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546 + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:27523 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:25547 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:46182 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546 Modified: trunk/refman-4.1/se-innodb-core.xml =================================================================== --- trunk/refman-4.1/se-innodb-core.xml 2009-11-05 18:10:41 UTC (rev 17479) +++ trunk/refman-4.1/se-innodb-core.xml 2009-11-05 19:48:52 UTC (rev 17480) Changed blocks: 1, Lines Added: 108, Lines Deleted: 126; 10512 bytes @@ -8260,151 +8260,133 @@ Some notes on the output sections: - + + SEMAPHORES + - - - SEMAPHORES - + + This section reports threads waiting for a semaphore and + statistics on how many times threads have needed a spin or a + wait on a mutex or a rw-lock semaphore. A large number of + threads waiting for semaphores may be a result of disk I/O, or + contention problems inside InnoDB. + Contention can be due to heavy parallelism of queries or + problems in operating system thread scheduling. Setting the + innodb_thread_concurrency + system variable smaller than the default value might help in + such situations. + - - This section reports threads waiting for a semaphore and - statistics on how many times threads have needed a spin or - a wait on a mutex or a rw-lock semaphore. A large number - of threads waiting for semaphores may be a result of disk - I/O, or contention problems inside - InnoDB. Contention can be due to heavy - parallelism of queries or problems in operating system - thread scheduling. Setting the - innodb_thread_concurrency - system variable smaller than the default value might help - in such situations. - - + + LATEST FOREIGN KEY + ERROR + - - - LATEST FOREIGN KEY ERROR - + + This section provides information about the most recent + foreign key constraint error. It is not present if no such + error has occurred. The contents include the statement that + failed as well as information about the constraint that failed + and the referenced and referencing tables. + - - This section provides information about the most recent - foreign key constraint error. It is not present if no such - error has occurred. The contents include the statement - that failed as well as information about the constraint - that failed and the referenced and referencing tables. - - + + LATEST DETECTED + DEADLOCK + - - - LATEST DETECTED DEADLOCK - + + This section provides information about the most recent + deadlock. It is not present if no deadlock has occurred. The + contents show which transactions are involved, the statement + each was attempting to execute, the locks they have and need, + and which transaction InnoDB decided to + roll back to break the deadlock. The lock modes reported in + this section are explained in + . + - - This section provides information about the most recent - deadlock. It is not present if no deadlock has occurred. - The contents show which transactions are involved, the - statement each was attempting to execute, the locks they - have and need, and which transaction - InnoDB decided to roll back to break - the deadlock. The lock modes reported in this section are - explained in . - - + + TRANSACTIONS + - - - TRANSACTIONS - + + If this section reports lock waits, your applications might + have lock contention. The output can also help to trace the + reasons for transaction deadlocks. + - - If this section reports lock waits, your applications - might have lock contention. The output can also help to - trace the reasons for transaction deadlocks. - - + + FILE I/O + - - - FILE I/O - + + This section provides information about threads that + InnoDB uses to perform various types of + I/O. The first few of these are dedicated to general + InnoDB processing. The contents also + display information for pending I/O operations and statistics + for I/O performance. + - - This section provides information about threads that - InnoDB uses to perform various types of - I/O. The first few of these are dedicated to general - InnoDB processing. The contents also - display information for pending I/O operations and - statistics for I/O performance. - + + On Unix, the number of threads is always 4. On Windows, the + number depends on the setting of the + innodb_file_io_threads system + variable. + - - On Unix, the number of threads is always 4. On Windows, - the number depends on the setting of the - innodb_file_io_threads - system variable. - - + + INSERT BUFFER AND ADAPTIVE HASH + INDEX + - - - INSERT BUFFER AND ADAPTIVE HASH INDEX - + + This section shows the status of the InnoDB + insert buffer and adaptive hash index. (See + , and + .) The contents include + the number of operations performed for each, plus statistics + for hash index performance. + - - This section shows the status of the - InnoDB insert buffer and adaptive hash - index. (See , and - .) The contents - include the number of operations performed for each, plus - statistics for hash index performance. - - + + LOG + - - - LOG - + + This section displays information about the + InnoDB log. The contents include the + current log sequence number, how far the log has been flushed + to disk, and the position at which InnoDB + last took a checkpoint. (See + .) The section also + displays information about pending writes and write + performance statistics. + - - This section displays information about the - InnoDB log. The contents include the - current log sequence number, how far the log has been - flushed to disk, and the position at which - InnoDB last took a checkpoint. (See - .) The section also - displays information about pending writes and write - performance statistics. - - + + BUFFER POOL AND + MEMORY + - - - BUFFER POOL AND MEMORY - + + This section gives you statistics on pages read and written. + You can calculate from these numbers how many data file I/O + operations your queries currently are doing. + - - This section gives you statistics on pages read and - written. You can calculate from these numbers how many - data file I/O operations your queries currently are doing. - - + + ROW + OPERATIONS + - - - ROW OPERATIONS - + + This section shows what the main thread is doing, including + the number and performance rate for each type of row + operation. + - - This section shows what the main thread is doing, - including the number and performance rate for each type of - row operation. - - - - -
Modified: trunk/refman-5.0/se-innodb-core.xml =================================================================== --- trunk/refman-5.0/se-innodb-core.xml 2009-11-05 18:10:41 UTC (rev 17479) +++ trunk/refman-5.0/se-innodb-core.xml 2009-11-05 19:48:52 UTC (rev 17480) Changed blocks: 1, Lines Added: 108, Lines Deleted: 126; 10512 bytes @@ -8238,151 +8238,133 @@ Some notes on the output sections: - + + SEMAPHORES + - - - SEMAPHORES - + + This section reports threads waiting for a semaphore and + statistics on how many times threads have needed a spin or a + wait on a mutex or a rw-lock semaphore. A large number of + threads waiting for semaphores may be a result of disk I/O, or + contention problems inside InnoDB. + Contention can be due to heavy parallelism of queries or + problems in operating system thread scheduling. Setting the + innodb_thread_concurrency + system variable smaller than the default value might help in + such situations. + - - This section reports threads waiting for a semaphore and - statistics on how many times threads have needed a spin or - a wait on a mutex or a rw-lock semaphore. A large number - of threads waiting for semaphores may be a result of disk - I/O, or contention problems inside - InnoDB. Contention can be due to heavy - parallelism of queries or problems in operating system - thread scheduling. Setting the - innodb_thread_concurrency - system variable smaller than the default value might help - in such situations. - - + + LATEST FOREIGN KEY + ERROR + - - - LATEST FOREIGN KEY ERROR - + + This section provides information about the most recent + foreign key constraint error. It is not present if no such + error has occurred. The contents include the statement that + failed as well as information about the constraint that failed + and the referenced and referencing tables. + - - This section provides information about the most recent - foreign key constraint error. It is not present if no such - error has occurred. The contents include the statement - that failed as well as information about the constraint - that failed and the referenced and referencing tables. - - + + LATEST DETECTED + DEADLOCK + - - - LATEST DETECTED DEADLOCK - + + This section provides information about the most recent + deadlock. It is not present if no deadlock has occurred. The + contents show which transactions are involved, the statement + each was attempting to execute, the locks they have and need, + and which transaction InnoDB decided to + roll back to break the deadlock. The lock modes reported in + this section are explained in + . + - - This section provides information about the most recent - deadlock. It is not present if no deadlock has occurred. - The contents show which transactions are involved, the - statement each was attempting to execute, the locks they - have and need, and which transaction - InnoDB decided to roll back to break - the deadlock. The lock modes reported in this section are - explained in . - - + + TRANSACTIONS + - - - TRANSACTIONS - + + If this section reports lock waits, your applications might + have lock contention. The output can also help to trace the + reasons for transaction deadlocks. + - - If this section reports lock waits, your applications - might have lock contention. The output can also help to - trace the reasons for transaction deadlocks. - - + + FILE I/O + - - - FILE I/O - + + This section provides information about threads that + InnoDB uses to perform various types of + I/O. The first few of these are dedicated to general + InnoDB processing. The contents also + display information for pending I/O operations and statistics + for I/O performance. + - - This section provides information about threads that - InnoDB uses to perform various types of - I/O. The first few of these are dedicated to general - InnoDB processing. The contents also - display information for pending I/O operations and - statistics for I/O performance. - + + On Unix, the number of threads is always 4. On Windows, the + number depends on the setting of the + innodb_file_io_threads system + variable. + - - On Unix, the number of threads is always 4. On Windows, - the number depends on the setting of the - innodb_file_io_threads - system variable. - - + + INSERT BUFFER AND ADAPTIVE HASH + INDEX + - - - INSERT BUFFER AND ADAPTIVE HASH INDEX - + + This section shows the status of the InnoDB + insert buffer and adaptive hash index. (See + , and + .) The contents include + the number of operations performed for each, plus statistics + for hash index performance. + - - This section shows the status of the - InnoDB insert buffer and adaptive hash - index. (See , and - .) The contents - include the number of operations performed for each, plus - statistics for hash index performance. - - + + LOG + - - - LOG - + + This section displays information about the + InnoDB log. The contents include the + current log sequence number, how far the log has been flushed + to disk, and the position at which InnoDB + last took a checkpoint. (See + .) The section also + displays information about pending writes and write + performance statistics. + - - This section displays information about the - InnoDB log. The contents include the - current log sequence number, how far the log has been - flushed to disk, and the position at which - InnoDB last took a checkpoint. (See - .) The section also - displays information about pending writes and write - performance statistics. - - + + BUFFER POOL AND + MEMORY + - - - BUFFER POOL AND MEMORY - + + This section gives you statistics on pages read and written. + You can calculate from these numbers how many data file I/O + operations your queries currently are doing. + - - This section gives you statistics on pages read and - written. You can calculate from these numbers how many - data file I/O operations your queries currently are doing. - - + + ROW + OPERATIONS + - - - ROW OPERATIONS - + + This section shows what the main thread is doing, including + the number and performance rate for each type of row + operation. + - - This section shows what the main thread is doing, - including the number and performance rate for each type of - row operation. - - - - -
Modified: trunk/refman-5.1/se-innodb-core.xml =================================================================== --- trunk/refman-5.1/se-innodb-core.xml 2009-11-05 18:10:41 UTC (rev 17479) +++ trunk/refman-5.1/se-innodb-core.xml 2009-11-05 19:48:52 UTC (rev 17480) Changed blocks: 1, Lines Added: 108, Lines Deleted: 126; 10512 bytes @@ -9380,151 +9380,133 @@ Some notes on the output sections: - + + SEMAPHORES + - - - SEMAPHORES - + + This section reports threads waiting for a semaphore and + statistics on how many times threads have needed a spin or a + wait on a mutex or a rw-lock semaphore. A large number of + threads waiting for semaphores may be a result of disk I/O, or + contention problems inside InnoDB. + Contention can be due to heavy parallelism of queries or + problems in operating system thread scheduling. Setting the + innodb_thread_concurrency + system variable smaller than the default value might help in + such situations. + - - This section reports threads waiting for a semaphore and - statistics on how many times threads have needed a spin or - a wait on a mutex or a rw-lock semaphore. A large number - of threads waiting for semaphores may be a result of disk - I/O, or contention problems inside - InnoDB. Contention can be due to heavy - parallelism of queries or problems in operating system - thread scheduling. Setting the - innodb_thread_concurrency - system variable smaller than the default value might help - in such situations. - - + + LATEST FOREIGN KEY + ERROR + - - - LATEST FOREIGN KEY ERROR - + + This section provides information about the most recent + foreign key constraint error. It is not present if no such + error has occurred. The contents include the statement that + failed as well as information about the constraint that failed + and the referenced and referencing tables. + - - This section provides information about the most recent - foreign key constraint error. It is not present if no such - error has occurred. The contents include the statement - that failed as well as information about the constraint - that failed and the referenced and referencing tables. - - + + LATEST DETECTED + DEADLOCK + - - - LATEST DETECTED DEADLOCK - + + This section provides information about the most recent + deadlock. It is not present if no deadlock has occurred. The + contents show which transactions are involved, the statement + each was attempting to execute, the locks they have and need, + and which transaction InnoDB decided to + roll back to break the deadlock. The lock modes reported in + this section are explained in + . + - - This section provides information about the most recent - deadlock. It is not present if no deadlock has occurred. - The contents show which transactions are involved, the - statement each was attempting to execute, the locks they - have and need, and which transaction - InnoDB decided to roll back to break - the deadlock. The lock modes reported in this section are - explained in . - - + + TRANSACTIONS + - - - TRANSACTIONS - + + If this section reports lock waits, your applications might + have lock contention. The output can also help to trace the + reasons for transaction deadlocks. + - - If this section reports lock waits, your applications - might have lock contention. The output can also help to - trace the reasons for transaction deadlocks. - - + + FILE I/O + - - - FILE I/O - + + This section provides information about threads that + InnoDB uses to perform various types of + I/O. The first few of these are dedicated to general + InnoDB processing. The contents also + display information for pending I/O operations and statistics + for I/O performance. + - - This section provides information about threads that - InnoDB uses to perform various types of - I/O. The first few of these are dedicated to general - InnoDB processing. The contents also - display information for pending I/O operations and - statistics for I/O performance. - + + On Unix, the number of threads is always 4. On Windows, the + number depends on the setting of the + innodb_file_io_threads system + variable. + - - On Unix, the number of threads is always 4. On Windows, - the number depends on the setting of the - innodb_file_io_threads - system variable. - - + + INSERT BUFFER AND ADAPTIVE HASH + INDEX + - - - INSERT BUFFER AND ADAPTIVE HASH INDEX - + + This section shows the status of the InnoDB + insert buffer and adaptive hash index. (See + , and + .) The contents include + the number of operations performed for each, plus statistics + for hash index performance. + - - This section shows the status of the - InnoDB insert buffer and adaptive hash - index. (See , and - .) The contents - include the number of operations performed for each, plus - statistics for hash index performance. - - + + LOG + - - - LOG - + + This section displays information about the + InnoDB log. The contents include the + current log sequence number, how far the log has been flushed + to disk, and the position at which InnoDB + last took a checkpoint. (See + .) The section also + displays information about pending writes and write + performance statistics. + - - This section displays information about the - InnoDB log. The contents include the - current log sequence number, how far the log has been - flushed to disk, and the position at which - InnoDB last took a checkpoint. (See - .) The section also - displays information about pending writes and write - performance statistics. - - + + BUFFER POOL AND + MEMORY + - - - BUFFER POOL AND MEMORY - + + This section gives you statistics on pages read and written. + You can calculate from these numbers how many data file I/O + operations your queries currently are doing. + - - This section gives you statistics on pages read and - written. You can calculate from these numbers how many - data file I/O operations your queries currently are doing. - - + + ROW + OPERATIONS + - - - ROW OPERATIONS - + + This section shows what the main thread is doing, including + the number and performance rate for each type of row + operation. + - - This section shows what the main thread is doing, - including the number and performance rate for each type of - row operation. - - - - -
Modified: trunk/refman-5.4/se-innodb-core.xml =================================================================== --- trunk/refman-5.4/se-innodb-core.xml 2009-11-05 18:10:41 UTC (rev 17479) +++ trunk/refman-5.4/se-innodb-core.xml 2009-11-05 19:48:52 UTC (rev 17480) Changed blocks: 1, Lines Added: 108, Lines Deleted: 127; 10712 bytes @@ -9079,152 +9079,133 @@ Some notes on the output sections: - + + SEMAPHORES + - - - SEMAPHORES - + + This section reports threads waiting for a semaphore and + statistics on how many times threads have needed a spin or a + wait on a mutex or a rw-lock semaphore. A large number of + threads waiting for semaphores may be a result of disk I/O, or + contention problems inside InnoDB. + Contention can be due to heavy parallelism of queries or + problems in operating system thread scheduling. Setting the + innodb_thread_concurrency + system variable smaller than the default value might help in + such situations. + - - This section reports threads waiting for a semaphore and - statistics on how many times threads have needed a spin or - a wait on a mutex or a rw-lock semaphore. A large number - of threads waiting for semaphores may be a result of disk - I/O, or contention problems inside - InnoDB. Contention can be due to heavy - parallelism of queries or problems in operating system - thread scheduling. Setting the - innodb_thread_concurrency - system variable smaller than the default value might help - in such situations. - - + + LATEST FOREIGN KEY + ERROR + - - - LATEST FOREIGN KEY ERROR - + + This section provides information about the most recent + foreign key constraint error. It is not present if no such + error has occurred. The contents include the statement that + failed as well as information about the constraint that failed + and the referenced and referencing tables. + - - This section provides information about the most recent - foreign key constraint error. It is not present if no such - error has occurred. The contents include the statement - that failed as well as information about the constraint - that failed and the referenced and referencing tables. - - + + LATEST DETECTED + DEADLOCK + - - - LATEST DETECTED DEADLOCK - + + This section provides information about the most recent + deadlock. It is not present if no deadlock has occurred. The + contents show which transactions are involved, the statement + each was attempting to execute, the locks they have and need, + and which transaction InnoDB decided to + roll back to break the deadlock. The lock modes reported in + this section are explained in + . + - - This section provides information about the most recent - deadlock. It is not present if no deadlock has occurred. - The contents show which transactions are involved, the - statement each was attempting to execute, the locks they - have and need, and which transaction - InnoDB decided to roll back to break - the deadlock. The lock modes reported in this section are - explained in . - - + + TRANSACTIONS + - - - TRANSACTIONS - + + If this section reports lock waits, your applications might + have lock contention. The output can also help to trace the + reasons for transaction deadlocks. + - - If this section reports lock waits, your applications - might have lock contention. The output can also help to - trace the reasons for transaction deadlocks. - - + + FILE I/O + - - - FILE I/O - + + This section provides information about threads that + InnoDB uses to perform various types of + I/O. The first few of these are dedicated to general + InnoDB processing. The contents also + display information for pending I/O operations and statistics + for I/O performance. + - - This section provides information about threads that - InnoDB uses to perform various types of - I/O. The first few of these are dedicated to general - InnoDB processing. The contents also - display information for pending I/O operations and - statistics for I/O performance. - + + The number of these threads are controlled by the + innodb_read_io_threads and + innodb_write_io_threads + parameters. See . + - - The number of these threads are controlled by the - innodb_read_io_threads - and - innodb_write_io_threads - parameters. See . - - + + INSERT BUFFER AND ADAPTIVE HASH + INDEX + - - - INSERT BUFFER AND ADAPTIVE HASH INDEX - + + This section shows the status of the InnoDB + insert buffer and adaptive hash index. (See + , and + .) The contents include + the number of operations performed for each, plus statistics + for hash index performance. + - - This section shows the status of the - InnoDB insert buffer and adaptive hash - index. (See , and - .) The contents - include the number of operations performed for each, plus - statistics for hash index performance. - - + + LOG + - - - LOG - + + This section displays information about the + InnoDB log. The contents include the + current log sequence number, how far the log has been flushed + to disk, and the position at which InnoDB + last took a checkpoint. (See + .) The section also + displays information about pending writes and write + performance statistics. + - - This section displays information about the - InnoDB log. The contents include the - current log sequence number, how far the log has been - flushed to disk, and the position at which - InnoDB last took a checkpoint. (See - .) The section also - displays information about pending writes and write - performance statistics. - - + + BUFFER POOL AND + MEMORY + - - - BUFFER POOL AND MEMORY - + + This section gives you statistics on pages read and written. + You can calculate from these numbers how many data file I/O + operations your queries currently are doing. + - - This section gives you statistics on pages read and - written. You can calculate from these numbers how many - data file I/O operations your queries currently are doing. - - + + ROW + OPERATIONS + - - - ROW OPERATIONS - + + This section shows what the main thread is doing, including + the number and performance rate for each type of row + operation. + - - This section shows what the main thread is doing, - including the number and performance rate for each type of - row operation. - - - - - In MySQL ¤t-series;, output from the standard Monitor includes additional sections compared to the output for Modified: trunk/refman-5.5/se-innodb-core.xml =================================================================== --- trunk/refman-5.5/se-innodb-core.xml 2009-11-05 18:10:41 UTC (rev 17479) +++ trunk/refman-5.5/se-innodb-core.xml 2009-11-05 19:48:52 UTC (rev 17480) Changed blocks: 1, Lines Added: 108, Lines Deleted: 127; 10712 bytes @@ -9050,152 +9050,133 @@ Some notes on the output sections: - + + SEMAPHORES + - - - SEMAPHORES - + + This section reports threads waiting for a semaphore and + statistics on how many times threads have needed a spin or a + wait on a mutex or a rw-lock semaphore. A large number of + threads waiting for semaphores may be a result of disk I/O, or + contention problems inside InnoDB. + Contention can be due to heavy parallelism of queries or + problems in operating system thread scheduling. Setting the + innodb_thread_concurrency + system variable smaller than the default value might help in + such situations. + - - This section reports threads waiting for a semaphore and - statistics on how many times threads have needed a spin or - a wait on a mutex or a rw-lock semaphore. A large number - of threads waiting for semaphores may be a result of disk - I/O, or contention problems inside - InnoDB. Contention can be due to heavy - parallelism of queries or problems in operating system - thread scheduling. Setting the - innodb_thread_concurrency - system variable smaller than the default value might help - in such situations. - - + + LATEST FOREIGN KEY + ERROR + - - - LATEST FOREIGN KEY ERROR - + + This section provides information about the most recent + foreign key constraint error. It is not present if no such + error has occurred. The contents include the statement that + failed as well as information about the constraint that failed + and the referenced and referencing tables. + - - This section provides information about the most recent - foreign key constraint error. It is not present if no such - error has occurred. The contents include the statement - that failed as well as information about the constraint - that failed and the referenced and referencing tables. - - + + LATEST DETECTED + DEADLOCK + - - - LATEST DETECTED DEADLOCK - + + This section provides information about the most recent + deadlock. It is not present if no deadlock has occurred. The + contents show which transactions are involved, the statement + each was attempting to execute, the locks they have and need, + and which transaction InnoDB decided to + roll back to break the deadlock. The lock modes reported in + this section are explained in + . + - - This section provides information about the most recent - deadlock. It is not present if no deadlock has occurred. - The contents show which transactions are involved, the - statement each was attempting to execute, the locks they - have and need, and which transaction - InnoDB decided to roll back to break - the deadlock. The lock modes reported in this section are - explained in . - - + + TRANSACTIONS + - - - TRANSACTIONS - + + If this section reports lock waits, your applications might + have lock contention. The output can also help to trace the + reasons for transaction deadlocks. + - - If this section reports lock waits, your applications - might have lock contention. The output can also help to - trace the reasons for transaction deadlocks. - - + + FILE I/O + - - - FILE I/O - + + This section provides information about threads that + InnoDB uses to perform various types of + I/O. The first few of these are dedicated to general + InnoDB processing. The contents also + display information for pending I/O operations and statistics + for I/O performance. + - - This section provides information about threads that - InnoDB uses to perform various types of - I/O. The first few of these are dedicated to general - InnoDB processing. The contents also - display information for pending I/O operations and - statistics for I/O performance. - + + The number of these threads are controlled by the + innodb_read_io_threads and + innodb_write_io_threads + parameters. See . + - - The number of these threads are controlled by the - innodb_read_io_threads - and - innodb_write_io_threads - parameters. See . - - + + INSERT BUFFER AND ADAPTIVE HASH + INDEX + - - - INSERT BUFFER AND ADAPTIVE HASH INDEX - + + This section shows the status of the InnoDB + insert buffer and adaptive hash index. (See + , and + .) The contents include + the number of operations performed for each, plus statistics + for hash index performance. + - - This section shows the status of the - InnoDB insert buffer and adaptive hash - index. (See , and - .) The contents - include the number of operations performed for each, plus - statistics for hash index performance. - - + + LOG + - - - LOG - + + This section displays information about the + InnoDB log. The contents include the + current log sequence number, how far the log has been flushed + to disk, and the position at which InnoDB + last took a checkpoint. (See + .) The section also + displays information about pending writes and write + performance statistics. + - - This section displays information about the - InnoDB log. The contents include the - current log sequence number, how far the log has been - flushed to disk, and the position at which - InnoDB last took a checkpoint. (See - .) The section also - displays information about pending writes and write - performance statistics. - - + + BUFFER POOL AND + MEMORY + - - - BUFFER POOL AND MEMORY - + + This section gives you statistics on pages read and written. + You can calculate from these numbers how many data file I/O + operations your queries currently are doing. + - - This section gives you statistics on pages read and - written. You can calculate from these numbers how many - data file I/O operations your queries currently are doing. - - + + ROW + OPERATIONS + - - - ROW OPERATIONS - + + This section shows what the main thread is doing, including + the number and performance rate for each type of row + operation. + - - This section shows what the main thread is doing, - including the number and performance rate for each type of - row operation. - - - - - In MySQL ¤t-series;, output from the standard Monitor includes additional sections compared to the output for Modified: trunk/refman-6.0.sav/se-innodb-core.xml =================================================================== --- trunk/refman-6.0.sav/se-innodb-core.xml 2009-11-05 18:10:41 UTC (rev 17479) +++ trunk/refman-6.0.sav/se-innodb-core.xml 2009-11-05 19:48:52 UTC (rev 17480) Changed blocks: 1, Lines Added: 108, Lines Deleted: 126; 10524 bytes @@ -8844,151 +8844,133 @@ Some notes on the output sections: - + + SEMAPHORES + - - - SEMAPHORES - + + This section reports threads waiting for a semaphore and + statistics on how many times threads have needed a spin or a + wait on a mutex or a rw-lock semaphore. A large number of + threads waiting for semaphores may be a result of disk I/O, or + contention problems inside InnoDB. + Contention can be due to heavy parallelism of queries or + problems in operating system thread scheduling. Setting the + innodb_thread_concurrency + system variable smaller than the default value might help in + such situations. + - - This section reports threads waiting for a semaphore and - statistics on how many times threads have needed a spin or - a wait on a mutex or a rw-lock semaphore. A large number - of threads waiting for semaphores may be a result of disk - I/O, or contention problems inside - InnoDB. Contention can be due to heavy - parallelism of queries or problems in operating system - thread scheduling. Setting the - innodb_thread_concurrency - system variable smaller than the default value might help - in such situations. - - + + LATEST FOREIGN KEY + ERROR + - - - LATEST FOREIGN KEY ERROR - + + This section provides information about the most recent + foreign key constraint error. It is not present if no such + error has occurred. The contents include the statement that + failed as well as information about the constraint that failed + and the referenced and referencing tables. + - - This section provides information about the most recent - foreign key constraint error. It is not present if no such - error has occurred. The contents include the statement - that failed as well as information about the constraint - that failed and the referenced and referencing tables. - - + + LATEST DETECTED + DEADLOCK + - - - LATEST DETECTED DEADLOCK - + + This section provides information about the most recent + deadlock. It is not present if no deadlock has occurred. The + contents show which transactions are involved, the statement + each was attempting to execute, the locks they have and need, + and which transaction InnoDB decided to + roll back to break the deadlock. The lock modes reported in + this section are explained in + . + - - This section provides information about the most recent - deadlock. It is not present if no deadlock has occurred. - The contents show which transactions are involved, the - statement each was attempting to execute, the locks they - have and need, and which transaction - InnoDB decided to roll back to break - the deadlock. The lock modes reported in this section are - explained in . - - + + TRANSACTIONS + - - - TRANSACTIONS - + + If this section reports lock waits, your applications might + have lock contention. The output can also help to trace the + reasons for transaction deadlocks. + - - If this section reports lock waits, your applications - might have lock contention. The output can also help to - trace the reasons for transaction deadlocks. - - + + FILE I/O + - - - FILE I/O - + + This section provides information about threads that + InnoDB uses to perform various types of + I/O. The first few of these are dedicated to general + InnoDB processing. The contents also + display information for pending I/O operations and statistics + for I/O performance. + - - This section provides information about threads that - InnoDB uses to perform various types of - I/O. The first few of these are dedicated to general - InnoDB processing. The contents also - display information for pending I/O operations and - statistics for I/O performance. - + + On Unix, the number of threads is always 4. On Windows, the + number depends on the setting of the + innodb_file_io_threads system + variable. + - - On Unix, the number of threads is always 4. On Windows, - the number depends on the setting of the - innodb_file_io_threads - system variable. - - + + INSERT BUFFER AND ADAPTIVE HASH + INDEX + - - - INSERT BUFFER AND ADAPTIVE HASH INDEX - + + This section shows the status of the InnoDB + insert buffer and adaptive hash index. (See + , and + .) The contents include + the number of operations performed for each, plus statistics + for hash index performance. + - - This section shows the status of the - InnoDB insert buffer and adaptive hash - index. (See , and - .) The contents - include the number of operations performed for each, plus - statistics for hash index performance. - - + + LOG + - - - LOG - + + This section displays information about the + InnoDB log. The contents include the + current log sequence number, how far the log has been flushed + to disk, and the position at which InnoDB + last took a checkpoint. (See + .) The section also + displays information about pending writes and write + performance statistics. + - - This section displays information about the - InnoDB log. The contents include the - current log sequence number, how far the log has been - flushed to disk, and the position at which - InnoDB last took a checkpoint. (See - .) The section also - displays information about pending writes and write - performance statistics. - - + + BUFFER POOL AND + MEMORY + - - - BUFFER POOL AND MEMORY - + + This section gives you statistics on pages read and written. + You can calculate from these numbers how many data file I/O + operations your queries currently are doing. + - - This section gives you statistics on pages read and - written. You can calculate from these numbers how many - data file I/O operations your queries currently are doing. - - + + ROW + OPERATIONS + - - - ROW OPERATIONS - + + This section shows what the main thread is doing, including + the number and performance rate for each type of row + operation. + - - This section shows what the main thread is doing, - including the number and performance rate for each type of - row operation. - - - - -