June 18, 2013

Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency

… used a 10GB key buffer. I used ALTER TABLE DISABLE KEYS and built the keys with sort via ALTER TABLE ENABLE KEYS. my.cnf [mysqld…/lib/mysql/mysql.sock user=justin innodb_buffer_pool_size=64G innodb_log_file_size=4G innodb_file_per_table innodb_stats…=2048 table_definition_cache=16384 innodb_flush_method=O_DIRECT key_buffer_size=10G # Disabling symbolic-links is recommended to prevent assorted…

Post: Benchmarking Percona Server TokuDB vs InnoDB

… innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 36G innodb_log_file_size = 4G innodb…_cache_size = 16M max_heap_table_size = 64M sort_buffer_size = 4M join_buffer_size = 4M thread_cache_size = 1000 query_cache… #*** MyISAM Specific options key_buffer_size = 8M read_buffer_size = 1M read_rnd_buffer_size = 4M bulk_insert_buffer_size = 8M myisam_sort_buffer_size = 8M…

Post: Virident vCache vs. FlashCache: Part 2

… below: #####fixed innodb options innodb_file_format = barracuda innodb_buffer_pool_size = 4G innodb_file_per_table = true innodb_data_file_path = ibdata1:100M innodb_flush_method = O_DIRECT innodb_log_buffer_size… server­id = 101 key_buffer_size = 8M read_buffer_size = 1M read_rnd_buffer_size = 4M bulk_insert_buffer_size = 8M myisam_sort_buffer_size = 8M…

Post: Beware: key_buffer_size larger than 4G does not work

… MyISAM, so they set key_buffer_size to 16G… and every few days MySQL crashes. Why ? Because key_buffer_size over 4GB in size… just fine until you have less than 4GB worth of key cache used and then it would crash. If you do… not only fix was not made available but even maximum key_buffer_size was not restricted to safe limit. Former would be…

Post: What to tune in MySQL Server after installation

… however if all of key_buffer is used over time – it is not rare to see key_buffer being set to 4G while combined size… much more sensitive to buffer size compared to MyISAM. MyISAM may work kind of OK with default key_buffer_size even with large data set but it will crawl with default innodb_buffer_pool_size. Also Innodb buffer pool…

Comment: What to tune in MySQL Server after installation

You comment that setting key_buffer to 4G is not uncommon. What if you need to go over 4G? I have noticed that no matter what value you set it at, it will always restrict you to a maximum of 4G.

Post: MySQL 5.6.7-RC in tpcc-mysql benchmark

… that innodb_buffer_pool_instances=8 makes a big difference on small buffer_pool sizes, while on bigger buffer_pool, innodb_buffer_pool_instances…_trx_commit = 1 innodb_buffer_pool_size = 125G innodb_buffer_pool_instances=8 innodb_log_file_size = 4G innodb_log_files_in_group… #*** MyISAM Specific options key_buffer_size = 8M read_buffer_size = 1M read_rnd_buffer_size = 4M bulk_insert_buffer_size = 8M myisam_sort_buffer_size = 8M…

Comment: Beware: key_buffer_size larger than 4G does not work

… a limit to the max size of the key_buffer_size, which is set to 4G. http://dev.mysql.com/doc/refman/5……there are ways around this limitation, you can add additional key buffers or (CACHE INDEXs) for individual tables after the server starts…: http://dev.mysql.com/doc/refman/5.0/en/multiple-key-caches.html Later! –Dave

Comment: Should you move from MyISAM to Innodb ?

… innodb_file_per_table is on, and data is compressed (key-buffer-size=4). Total db content is only 15G. Our Inserts… (),(),(),…). I set the innodb_buffer_pool_size to 1G (having 4G ram) which seems to be the highest buffer allowed. if exeeded, mysql…

Comment: What to tune in MySQL Server after installation

key_buffer has some internal implementation issues which limits its size to 4G. These are to be fixed in one of next MySQL versions but currently you should stick to this size.