… innodb_buffer_pool_size=64G innodb_log_file_size=4G innodb_file_per_table innodb_stats_on_metadata=off innodb_file_format=barracuda innodb_log_buffer_size=32M innodb…tmpdir=/dev/shm innodb_undo_logs=32 innodb_old_blocks_time=0 table_open_cache=2048 table_definition_cache=16384 innodb_flush_method=…
Post: Implementing SchemaSpy in your MySQL environment
June 4, 2013 By 2 Comments
… of metadata files. Installation of SchemaSpy and Dependencies Download the latest copy of SchemaSpy jar file (5.0.0 at time of writing…) unsigned NOT NULL AUTO_INCREMENT, PRIMARY KEY (`parent_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 CREATE TABLE `child_A` ( `id` int(10… your metadata file. Donate – This is free software and John Currier asks for donations so he can justify the time spent maintaining…
Post: Migrating between MySQL schemas with Percona Xtrabackup
June 10, 2013 By 2 Comments
… pool. Note that this can be somewhat mitigated using innodb_old_blocks_time, but that is outside the scope of this post… a quick refresher, Xtrabackup works by copying the dirty tablespace files while streaming the redo-logs to ensure that all transactions… time. When running Percona Server, you can utilize the –export flag during the –apply-logs phase and then re-import those files…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… time I tried, I got some variant of this message: 130606 2:22:41 [ERROR] /usr/libexec/mysqld: Incorrect information in file: ‘./mysql/servers.frm’ ERROR: 1033 Incorrect information in file: ‘./mysql/servers.frm’ Running mysql_install… –skip-grant-tables and insert a few rows into an InnoDB table, but trying to run a simple mysqlslap just hung…
Comment: How to calculate a good InnoDB log file size
May 21, 2013 By 38 Comments
… is far cheaper in modern versions of InnoDB: https://blogs.oracle.com/mysqlinnodb/entry/innodb_recovery_is_now_faster And from the…/en/innodb-performance-recovery.html “If you kept the size of your redo log files artificially low because recovery took a long time, you can consider increasing the file size.”
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
… are related to 60-sec checkpoint interval, as TokuDB does time-based checkpoints. These drops are quite concerning, and it might… = keep_average innodb_file_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
…cache”, “FlashCache”, “vCache with no time-based flushing”, and “vCache with time-based flushing.” As the images …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…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
…DIRECT innodb_log_buffer_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_file_per_table = true innodb_read…shutdown=1 –max-time=120 –max-requests=0 –percentile=99 –mysql-user=root –mysql-db=sbtest8t1M –mysql-table-engine=INNODB –mysql-…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
… scenario. Percona Server 5.5 outperforms MySQL in about 2x times. Both MySQL 5.5.30 and MySQL 5.6.11… = 1 innodb_log_buffer_size=128M innodb_max_dirty_pages_pct=80 innodb_file_format=barracuda innodb_file_per_table innodb_read_io_threads = 8 innodb_write_io_threads = 8 innodb_io…
Post: Percona XtraBackup 2.0.7 for MySQL available for download
May 6, 2013 By 1 Comment
…, 5.6-style buffer pool dump files). Percona XtraBackup has implemented support for the InnoDB Buffer Pool Preloading introduced in MySQL 5…-copy-interval. Making the interval configurable allows to reduce the time between checks which can prevent XtraBackup failures that are caused… well. Bug fixed #1169509. innobackupex wasn’t handling the innodb_data_file_path option which could cause backup to fail. Bug fixed…
