Hi Piano as I have just finished tuning MYSQL for a week or two now here are my findings about the Tuner and MYSQL

Query Cache Size = this is the size of the pool for query cache. Your query cache is disabled so you need to turn it on and set a size. It says > 8 megs a good start for your server would be 256M , I found I need at least that much on my 2gig and 8gig servers. Its best to start low and tune up then make giant jumps, but sometimes your wasting time as I have already noticed over a week of upping it over and over some settings.

Join Buffer Size = you can go up to 256kb, a lot of people like to push this up to 2MB

Know that some of these buffers are PER connection, so if you get a lot of users that can really eat up ram FAST and crash your server. Also based on my research, the type of ram used once you pass 256kb is 37x slower then that first bit of ram.
So MORE is not always better for MYSQL, dont overtune your server way out of sync with norms or risk loss of performance.

From Monty Taylor “if buffer is set to over 256K, it uses mmap() instead of malloc() for memory allocation. Actually – this is a libc malloc thing and is tunable, but defaults to 256k. From the manual:” . He goes on in a further to shows that impact > 256K for a buffer is 37x slower. This applies to all per session buffers, not just sort buffer.

So I tried this at up to 2M dropped it back to 128 (default) or 256kb

Also the Tuner will ask you for ENDLESS RAM for join_buffer_size, you can keep going up to 30megs etc and it will not stop because your tables will never use Index with joins, and this is not a way to fix that, you would need to recode your mysql not jack up JOINS ram. 179177 joins without is just WAY too many to try to buffer this.

tmp_table_size (> 32M) = this one is a basic pool of cache, jack it up no problem
max_heap_table_size = should be set the same as it

thread_cache_size (start at 4) = I am at 50 so id at least goto 20 for this

table_cache (> 64) = I am at 5000 on a 2gig server so I am sure you can use that much at least

innodb_buffer_pool_size (>= 145M) = simple pool, you can juice this one no problem also follows its directions

Hi Piano as I have just finished tuning MYSQL for a week or two now here are my findings about the Tuner and MYSQL

Query Cache Size = this is the size of the pool for query cache. Your query cache is disabled so you need to turn it on and set a size. It says > 8 megs a good start for your server would be 256M , I found I need at least that much on my 2gig and 8gig servers. Its best to start low and tune up then make giant jumps, but sometimes your wasting time as I have already noticed over a week of upping it over and over some settings.

Join Buffer Size = you can go up to 256kb, a lot of people like to push this up to 2MB

Know that some of these buffers are PER connection, so if you get a lot of users that can really eat up ram FAST and crash your server. Also based on my research, the type of ram used once you pass 256kb is 37x slower then that first bit of ram.
So MORE is not always better for MYSQL, dont overtune your server way out of sync with norms or risk loss of performance.

From Monty Taylor “if buffer is set to over 256K, it uses mmap() instead of malloc() for memory allocation. Actually – this is a libc malloc thing and is tunable, but defaults to 256k. From the manual:” . He goes on in a further to shows that impact > 256K for a buffer is 37x slower. This applies to all per session buffers, not just sort buffer.

So I tried this at up to 2M dropped it back to 128 (default) or 256kb

Also the Tuner will ask you for ENDLESS RAM for join_buffer_size, you can keep going up to 30megs etc and it will not stop because your tables will never use Index with joins, and this is not a way to fix that, you would need to recode your mysql not jack up JOINS ram. 179177 joins without is just WAY too many to try to buffer this.

tmp_table_size (> 32M) = this one is a basic pool of cache, jack it up no problem
max_heap_table_size = should be set the same as it

thread_cache_size (start at 4) = I am at 50 so id at least goto 20 for this

table_cache (> 64) = I am at 5000 on a 2gig server so I am sure you can use that much at least

innodb_buffer_pool_size (>= 145M) = simple pool, you can juice this one no problem also follows its directions

too large a query cache can be more of a negative than positive as mysql needs to check the entire buffer everytime a new query is sent its way. Start low ie. 32mb or 64mb and see how it goes. I've only just started looking into mysql optimization and this is the first thing I learn-ed today :D