June 18, 2013

Post: What MySQL buffer cache hit rate should you target

in trouble) or “OS file reads”, “OS file writes” from SHOW INNODB STATUS for Innodb tables. In MySQL 5.0+ you can also use Innodb_data_reads, and Innodb

Post: Innodb Performance Optimization Basics

innodb_file_per_table – If you do not have too many tables use this option, so you will not have uncontrolled innodbin locking in 5.0 and even more to come with MySQL 5

Post: Fishing with dynamite, brought to you by the randgen and dbqp

howhave been reused many times (including for two of these bugs!) This brings us to our first bug: mysql process crashes after setting innodbto ensure that the server used –innodb_file_per_table and that we used Xtrabackup’s –parallel option. I also wanted to

Post: Lost innodb tables, xfs and binary grep

how data was lost: MySQL had a dedicated partition on XFS file system Server was running innodb_file_per_table…partition was scanned in like 5 minutes and all 4G of innodb pages were successfully written to a …if you happen to have a lot of data to scan and you have to choose between matching text…

Post: Reasons for run-away main Innodb Tablespace

MySQL With innodb_file_per_table option but your ibdata1 file which holds main (or system) tablespace haveINNODB STATUS this is how you can see Insert Buffer Size: Ibuf: size 108931, free list len 64619, seg size 173551, In…even 5 minute transaction may be considered long as it will be enough to

Post: XtraDB/InnoDB CPU bound benchmarks on 24cores server

MySQL-5.1.30 with InnoDBinnodb_file_per_table=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=512M innodb_status_file=0 innodbInnoDB, but nothing special to be proud of. We definitely we will look how to

Post: SHOW INNODB STATUS walk through

In MySQL 5 number of Innodb performance counters were exported and now available inInnodb has written in log files since system tablespace creation. You can also see up to which point logs have been flushed – so how

Post: A case for MariaDB's Hash Joins

MySQL flavors. MySQL 5.5.24 Configuration innodb_file_per_table=1 innodb_file_format=barracuda innodb_log_file_size=512M innodb_log_files_in_group=2 innodb_flush_log_at_trx_commit=2 innodb

Post: Heikki Tuuri answers to Innodb questions, Part II

MySQL 5.0 vs 4.1 has a lot of performance differences and not all of them are Innodbtable, but how long will this take? Is there a facility we can run to show any table / index fragmentation, without having to

Post: High-Performance Click Analysis with MySQL

to use InnoDB/XtraDB tables… Optimize For I/O It is pretty much inevitable: if you do this kind of data processing in MySQLfiles and use the CSV engine so you have an SQL interface to it (the meta-tableshave to think about how to avoid enormous tables that are hard to