… –session-init-query command-line option, we set the option innodb_fake_changes to prevent INSERTs, UPDATEs, and DELETEs from corrupting… server. You will need Percona Server in order to use innodb_fake_changes. Thread pool Percona Playback added a connection pool… were split into chunks, each containing roughly 1M queries. We warmed the cold database with the first chunk and replayed the…
Post: My "hot" list for next InnoDB features
March 30, 2009 By 18 Comments
Many InnoDB scalability problems seem fixed in InnoDB-plugin-1.0.3 and I expect InnoDB-plugin will run fine on 16-24…. You can use custom queries by primary / secondary key to “warm up” part of table, but this solution is ugly and… asked what are our current plans about XtraDB with recent InnoDB-pluging release, as performance improvements in plugin may make XtraDB…
Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1
January 8, 2007 By 117 Comments
… was a popular myth that MyISAM is faster than InnoDB in reads, as InnoDB is transactional, supports Foreign Key and has an… MyISAM / InnoDB: libexec/mysqld –no-defaults –user=root –key-buffer-size=1500M –innodb-buffer-pool-size=1500M –innodb-log-file-size=100M –innodb-thread…, 128, 256 concurrent threads. 3. For each thread perform a warm-up run (duration 180 sec), and then run three effective…
Post: How well does your table fits in innodb buffer pool ?
December 9, 2010 By 12 Comments
…_id = innodb_sys_tables.id JOIN innodb_index_stats ON innodb_index_stats.table_name = innodb_sys_tables.name AND innodb_sys_indexes.name = innodb_index_stats.index_name AND innodb_index_stats.table_schema = innodb… these stats during warmup to see what is really getting warmed up first as well as how buffer pool is affected…
Post: InnoDB compression woes
May 20, 2011 By 14 Comments
InnoDB compression is getting some traction, and I see quite contradictory … this will report us results each 10 sec. After initial warm-up the throughput for regular tables are stabilized on level… 7%. Obviously we have some mutex serialization problem. Analyzing SHOW INNODB STATUS (SEMAPHORES) for workload with compression tables we can see…
Comment: XtraDB feature: save / restore buffer pool
January 27, 2010 By 20 Comments
Vadim, this means we can make a BufferPool-Dump, run the server 2 hours, crash it and after restarting (and innodb‘s recovery) and dumping the BufferPool back to the RAM we have an warm InnoDB instance with no stale data? And no other problems?
Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark
March 11, 2013 By 7 Comments
…than the data but underlying IO is fast (a warm FS cache reduces IO cost significantly) And finally, testing… 3776369 | | INNODB_BUFFER_POOL_READS | 191571 | | INNODB_DATA_PENDING_READS | 0 | | INNODB_DATA_READ | 3140882432 | | INNODB_DATA_READS | 191581 | | INNODB_PAGES_READ | 191570 | | INNODB_ROWS…
Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact
March 12, 2012 By 12 Comments
I have been working with Peter in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in the same way this blog post is aimed at a new optimizer enhancement Index Condition …
Post: XtraDB feature: save / restore buffer pool
January 20, 2010 By 20 Comments
… to warm cache. In case with the server crash, it is even worse, you need to wait possible long time on InnoDB…, in that post you can see InnoDB recovery took 1h to accomplish) and after that warm caches. Second, it is useful for… there http://www.percona.com/docs/wiki/percona-xtradb:patch:innodb_lru_dump_restore (Yasufumi names it LRU dump/restore, because…
Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5
April 4, 2012 By 4 Comments
… in-memory workload, the InnoDB buffer pool size is set to 6G and the buffer pool was warmed up, so that the… IO bound workload, the InnoDB buffer pool size is set to 1G and the buffer pool was not warmed up, so that… 2.2G Innodb_data_reads 329115 355323 143808 335526 16164 15506 Innodb_pages_read 329115 355323 143808 358308 144798 144881 Innodb_rows_read…
