diff options
| author | Owen Jacobson <owen.jacobson@grimoire.ca> | 2013-01-23 14:22:53 -0500 |
|---|---|---|
| committer | Owen Jacobson <owen.jacobson@grimoire.ca> | 2013-01-23 14:22:53 -0500 |
| commit | f06c9ba1f705d4fa7c51cebc1d2468b158a21b14 (patch) | |
| tree | 9d64f2d5427325d65dbfde72576d73b3b0c19c48 /wiki | |
| parent | 5b82b04a091b54322f595533f28675cf3d601159 (diff) | |
Formatting fixup (thanks, @SurprisingEdge!)
Diffstat (limited to 'wiki')
| -rw-r--r-- | wiki/mysql/choose-something-else.md | 18 |
1 files changed, 8 insertions, 10 deletions
diff --git a/wiki/mysql/choose-something-else.md b/wiki/mysql/choose-something-else.md index 9105d62..5515e7f 100644 --- a/wiki/mysql/choose-something-else.md +++ b/wiki/mysql/choose-something-else.md @@ -157,16 +157,14 @@ experience, blog articles of varying quality, and consultants. considering every entry in the cache. This cache also uses MySQL's LRU implementation, which has its own performance problems during eviction that get worse with larger cache sizes. -* Memory-management settings, including `key_buffer_size` and - `innodb_buffer_pool_size`, have non-linear relationships with performance. - The - [standard](http://www.mysqlperformanceblog.com/2006/09/29/what-to-tune-in-mysql-server-after-installation/) - [advice](http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimization-basics/) - advises making whichever value you care about more to a large value, but - this can be counterproductive if the related data is larger than the pool - can hold: MySQL is once again bad at discarding old buffer pages when the - buffer is exhausted, leading to dramatic slowdowns when query load reaches a - certain point. +* Memory-management settings, including `key_buffer_size` and `innodb_buffer_pool_size`, + have non-linear relationships with performance. The [standard](http://www.mysqlperformanceblog.com/2006/09/29/what-to-tune-in-mysql-server-after-installation/) + [advice](http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimization-basics/) advises + making whichever value you care about more to a large value, but this can be + counterproductive if the related data is larger than the pool can hold: + MySQL is once again bad at discarding old buffer pages when the buffer is + exhausted, leading to dramatic slowdowns when query load reaches a certain + point. * This also affects filesystem tuning settings such as `table_open_cache`. * InnoDB, out of the box, comes configured to use one large (and automatically growing) tablespace file for all tables, complicating backups and storage |