From f06c9ba1f705d4fa7c51cebc1d2468b158a21b14 Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Wed, 23 Jan 2013 14:22:53 -0500 Subject: Formatting fixup (thanks, @SurprisingEdge!) --- wiki/mysql/choose-something-else.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) (limited to 'wiki/mysql/choose-something-else.md') 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 -- cgit v1.2.3