June 19, 2013

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

… post in this series. Regardless, when the working set fits in memory, InnoDB almost always performs better, at least for this workload… innodb_stats_on_metadata=off innodb_file_format=barracuda innodb_log_buffer_size=32M innodb_buffer_pool_instances=16 metadata_locks_hash_instances=32 table_open

Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL

… bug fixes in it. All of Percona’s software is open-source and free, all the details of the release can… between the directory and file name components in a bitmap file name could stop the server starting if the innodb_data_home_dir… a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug…

Post: Percona Server 5.6.11-60.3 first Release Candidate now available

… Server 5.6 series. All of Percona’s software is open-source and free, all the details of the release can… between the directory and file name components in a bitmap file name could stop the server starting if the innodb_data_home_dir… a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug…

Post: Benchmarking Percona Server TokuDB vs InnoDB

innodb_file_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodbinnodb options (fixed) port = 3306 back_log = 50 max_connections = 2000 max_prepared_stmt_count=500000 max_connect_errors = 10 table_open… good settings out-…

Post: Virident vCache vs. FlashCache: Part 2

sets of experiments. First, the baseline configuration plus: innodb_read_io_threads = 16 innodbinnodb 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… table_open_cache = 10240 …

Post: Percona XtraBackup 2.0.7 for MySQL available for download

… XtraBackup can spend a lot of time opening all the tablespaces. Optimization has been implemented … innobackupex would fail if the SQL_MODE was set to ANSI_QUOTES. Bug fixed #945161. Missing…fixed #1169509. innobackupex wasn’t handling the innodb_data_file_path option which could cause backup to fail…

Post: Announcing Percona XtraBackup 2.1.1 GA

sets and mission-critical applications that cannot tolerate long periods of downtime. Offered free as an open… command line client. Support for InnoDB 5.0 and InnoDB 5.1 builtin has been removed …fixed #1168513. Percona XtraBackup would leave xbtemp temp files behind due to a typo. Bug fixed #1172016…

Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available

file (my.cnf). Bugs fixed #1160047 and #1086978 (Raghavendra D Prabhu). Donor node would run XtraBackup indefinitely when xtrabackup tmpdir was set…). If variable innodb_thread_concurrency has been defined to throttle InnoDB access, and …All of Percona’s software is open-source and free. Release notes…

Post: How innodb_open_files affects performance

…- innodb_open_files which defines how many files Innodb will keep open while working in innodb_file_per_table mode. Unlike MyISAM Innodb does not have to keep open fileset of empty tables which is about 10 times smaller for MyISAM. I found no significant difference whatever limit of open files

Comment: MySQL File System Fragmentation Benchmarks

Kevin, table_cache is not the only one you should be looking for – if you’re using innodb_file_per_table setting innodb_open_files also need to be set high enough so no reopens are required. I specially kept those default so we get the open/reopen overhead factored in.