forked from percona/pmm-doc
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Paul Jacobs
committed
Aug 26, 2021
1 parent
d94f96d
commit 1f540df
Showing
6 changed files
with
25 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,17 @@ | ||
# Advisors | ||
# Advisors | ||
|
||
## InnoDB Flush Method May Not Be Optimal | ||
|
||
### Problem Description | ||
|
||
By default, InnoDB's log buffer is written out to the log file at each transaction commit and a flush-to-disk operation is performed on the log file, which enforces ACID compliance. In the event of a crash, if you can afford to lose a second's worth of transactions, you can achieve better performance by setting `__innodb_flush_log_at_trx_commit__` to either 0 or 2. If you set the value to 2, then only an operating system crash or a power outage can erase the last second of transactions. This can be very useful on slave servers, where the loss of a second's worth of data can be recovered from the master server if needed. | ||
|
||
### Links and Further Reading | ||
|
||
[Variables](http://dev.mysql.com/doc/mysql/en/innodb-parameters.html#optvar_innodb_flush_log_at_trx_commit) MySQL Manual: [InnoDB Performance Tuning Tips](http://dev.mysql.com/doc/mysql/en/optimizing-innodb.html) | ||
|
||
### Expression | ||
|
||
``` | ||
(%innodb_flush_log_at_trx_commit% == THRESHOLD) | ||
``` |
15 changes: 0 additions & 15 deletions
15
docs/using/advisors/innodb_log_buffer_flushed_to_disk_after_each_trx.md
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters