June 20, 2013

Post: Benchmarking Percona Server TokuDB vs InnoDB

… = 8M myisam_sort_buffer_size = 8M myisam_max_sort_file_size = 10G #myisam_max_extra_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover socket=/var/lib/mysql/mysql.sock user=root skip-grant-tables TokuDB-related options are all…

Post: Virident vCache vs. FlashCache: Part 2

…The base MySQL configuration (configuration A) appears below: #####fixed innodb options innodb_file_format = barracuda innodb_buffer_pool_size = 4G …buffer_size = 4M bulk_insert_buffer_size = 8M myisam_sort_buffer_size = 8M myisam_max_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover

Post: Ultimate MySQL variable and status reference list

myisam_mmap_sizeblogpercona.commanual myisam_recoverblogpercona.commanual myisam_recover_optionsblogpercona.commanual myisam_recover_optionsblogpercona.commanual myisam_repair_threadsblogpercona.commanual myisam_sort_buffer_sizeblogpercona.commanual myisam_stats_methodblogpercona.commanual myisam

Post: Using MyISAM in production

… were recently number of posts about MyISAM, for example Arjen wrote pretty nice article about MyISAM features so I thought I would… hours to check recover our tables. If this happened make sure you have decent myisam_sort_buffer_size and large myisam_max_sort… which can take even longer. Be careful with myisam_recover. This is great option to automate recovery but it can give you couple…

Post: MySQL Crash Recovery

… or which may seriously affect MySQL Performance. MyISAM Corruption – If you’re writting to MyISAM tables there is very large chance of… MySQL with myisam_recover option which will make sure all improperly closed MyISAM tables are checked first time it is accessed. This option is however…

Post: Concatenating MyISAM files

…/test# myisamchk -rq test_concat – check record delete-chain – recovering (with sort) MyISAM-table ‘test_concat’ Data records: 3 – Fixing index 1… MyISAM-table ‘test_concat’ is not fixed because of errors Try fixing it by using the –safe-recover (-o), the –force (-f) option or by not using the –quick (-q) flag root@django:/var/lib/mysql/test# myisamchk -r test_concat – recovering (with sort) MyISAM

Post: Recovering Innodb table Corruption

…(10) unsigned NOT NULL AUTO_INCREMENT, -> PRIMARY KEY (`id`) -> ) ENGINE=MYISAM; Query OK, 0 rows affected (0.03 sec) mysql> insert… table back to Innodb after restarting without innodb_force_recovery option. You can also rename the old table in case you… all data it could recover to MyISAM table. Using series of queries with LIMIT can be handly if you recover manually: mysql> insert…

Post: How to recover a single InnoDB table from a Full Backup

… particular scenario is faster to recover single tables than a full backup. This is easy with MyISAM but if your tables are… the service. In the second step the use of –export option runs a recovery process on the backup with innodb_fast…! Conclusion: As we learned , you can also recover single InnoDB table as with MyISAM but knowing in advance that there are some…

Post: Aligning IO on a hard disk RAID – the Benchmarks

… this case). When I have mounted the partition with inode64 option however, the effect disappeared and performance without LVM was slightly…_insert_buffer_size = 8M myisam_sort_buffer_size = 8M myisam_max_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover skip-grant-tables Amount…

Post: MySQL 5.6.7-RC in tpcc-mysql benchmark

… #*** 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 myisam_max_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover user=root skip-grant…