2012-04-18, 00:32
(2012-04-17, 08:56)Finchy Wrote: Ah, thanks! I wasn't sure what they all meant or how they affecte it and was pretty much guessing! I assumed the M was MB....is that correct?
So would I be better with;
tmp_table_size= 35M
query_cache_limit = 2M ?
query_cache_size = 32M
innodb_buffer_pool_size = ?
max_allowed_packet = ?
max_heap_table_size = 35M
Yep M = MB. You can alternatively also use K = KB if you wish.
This is what I use
Code:
tmp_table_size = 16M
max_heap_table_size = 16M
innodb_buffer_pool_size = 128M
max_allowed_packet = 1M
query_cache_size is fine and thats the one which has the most impact on performance, and if XBMC is the only thing you are using MySQL for I would be super surprised if you end up using that much. The wonko thing with query cache is, its only good as long as the underlying data is not updated, the instant you have something updating the table underneath, the qcache gets invalidated and MySQL goes back to disk to do the select.
The good thing is, the majority of the XBMC interactions with MySQL I was able to see were selects.