… noatime and nodiratime options if you’re using innodb_file_per_table and a lot of tables though benefit of these is minor. Also make… may suffer. innodb_file_per_table – If you do not have too many tables use this option, so you will not have uncontrolled innodb main tablespace… row level replication. There are bunch of other options you may want to tune but lets focus only on Innodb ones today…
Post: Ultimate MySQL variable and status reference list
January 8, 2011 By 4 Comments
…innodb_doublewriteblogpercona.commanual innodb_fast_shutdownblogpercona.commanual innodb_file_formatblogpercona.commanual innodb_file_format_checkblogpercona.commanual innodb_file_format_maxblogpercona.commanual innodb_file_per_tableblogpercona.commanual innodb…
Comment: Should you move from MyISAM to Innodb ?
February 1, 2010 By 59 Comments
…mysqldump and innodb file-per table. Our “Database File-Per-Table Archives” web site summarizes like this: “31 Hosts 90 Databases 2919 Tables 91 Dates 354456 Backup Files” … to you, icrease the use of MASTER-SLAVE replication, and use file-per-table management. Then restore-from-backup can be done …
Post: Shard-Query EC2 images available
May 11, 2011 By 2 Comments
…INNODB innodb-buffer-pool-instances=2 innodb-buffer-pool-size=5600M innodb-file-format=barracuda innodb-file-per-table innodb-flush-log-at-trx-commit=1 innodb-flush-method=O_DIRECT innodb…
Post: Percona Toolkit Webinar followup Q&A
December 19, 2012 By 1 Comment
… original table is left unmodified. The same attendee asked about any performance differences when using the tool with or without innodb_file_per_table, and… won’t be recovered when the auxiliary table is dropped unless you’re using innodb_file_per_table. Q: Does pt-online-schema-change work… differences between two (or more) servers, if using statement based replication, it is possible that new differences are introduced while the…
Post: MySQL Crash Recovery
July 30, 2006 By 30 Comments
… and innodb_buffer_pool_size affect recovery time significantly as well as your workload. I should also mention if you have innodb_file_per_table=1 your recovery speed will depend on number of Innodb tables you have, as well as… out of sync with database content. This will sometimes break replication but if you’re just planning on using binary log…
Post: Fishing with dynamite, brought to you by the randgen and dbqp
November 16, 2011 By Leave a Comment
… transactional grammars that were originally written for testing Drizzle’s replication system have been reused many times (including for two of… following options in the test case: server_requirements = [["--innodb-dict-size-limit=200k --table-open-cache=10"]] Granted, these are insanely small… this bug, we needed to ensure that the server used –innodb_file_per_table and that we used Xtrabackup’s –parallel option. I also…
Comment: MySQL on Amazon RDS part 2: Determining Peak Throughput
March 28, 2011 By 4 Comments
…innodb_data_file_path ibdata1:10M:autoextend innodb_data_home_dir /rdsdbdata/db/innodb innodb_doublewrite ON innodb_fast_shutdown 1 innodb_file_format Antelope innodb_file_format_check Barracuda innodb_file_per_table…
Post: Review of MySQL 5.6 Defaults Changes
October 8, 2012 By 10 Comments
… just default at 2000 ? innodb_file_per_table =1 Great! We found it is better choice in 95%+ of installations innodb_log_file_size = 48M This is still too small for any real load but a lot better than 5MB. Good to see innodb… as replication will be badly out of sync if slave is to crash. The recommendation to use master_info_repository=table is…
Post: Quickly finding unused indexes (and estimating their size)
December 5, 2012 By 2 Comments
… just a slave somewhere (just be careful not to break replication!). mysql> create schema index_analysis; If our index_statistics are…. If you use innodb_file_per_table, then you can rebuild the tablespace for your table by simply doing: mysql> alter table mytable ENGINE=Innodb; However, this…
