…:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 36G innodb_log_file_size = 4G innodb_log_files_in_group = 2 innodb_log_block_size=4096 #####plugin options innodb_read…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
…100M:autoextend innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_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_io_threads = 8 innodb…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
…innodb_data_file_path = ibdata1:100M innodb_flush_method = O_DIRECT innodb_log_buffer_size = 128M innodb_flush_log_at_trx_commit = 1 innodb…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
April 15, 2013 By
… is another issue in InnoDB transaction processing that notably affects MySQL performance – for every transaction InnoDB creates a read view and allocates memory… the heap for that allocation is destroyed on each commit and thus the read view memory is reallocated on the next transaction…
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
April 12, 2013 By 3 Comments
… still stands in the way of InnoDB scalability is the trx_list scan on consistent read view creation. It was originally reported… transactions are seen in the view later. To this end, InnoDB scans trx_list (i.e. the list of currently open… been committed at the current point in time, and thus should not be visible in the consistent read. For the REPEATABLE_READ isolation…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
… innodb_flush_log_at_trx_commit = 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…
Comment: Is Synchronous Replication right for your app?
May 16, 2013 By 18 Comments
…: that seems like a hard problem to solve for standalone Innodb, let alone Galera. I had considered a job queue system in Innodb in the past that, in absence of a ‘SKIP LOCKED’ feature, would use READ-UNCOMMITTED to find… trx and had updated some meta field, but had not committed) and so could gracefully find rows that had not been…
Post: Differences between READ-COMMITTED and REPEATABLE-READ transaction isolation levels
August 28, 2012 By 3 Comments
… READ-COMMITTED and REPEATABLE-READ, and they are all related to locking. Extra locking (not gap locking) It is important to remember that InnoDB… levels InnoDB creates locks over every index entry scanned. The difference between the levels is that once the statement completes in READ COMMITTED mode, the locks are released for the entries that did not match the scan. Note that InnoDB does not…
Post: READ-COMMITED vs REPETABLE-READ in tpcc-like load
February 11, 2010 By 6 Comments
… in InnoDB : Any real performance improvement when using READ COMMITED isolation level ? and in Repeatable read versus read committed for InnoDB . Serge in his post explains why READ COMMITED… XtraDB-9 ( based on InnoDB-plugin 1.0.6) So there are results: For 1000w: There READ-COMMITED seems more preferable, however difference…
Post: Heikki Tuuri Innodb answers - Part I
October 26, 2007 By 19 Comments
… transaction isolation level READ COMMITTED, then InnoDB normally does not lock the ‘gaps’, and it does not lock rows whose latest committed version does…. INNODB uses fuzzy checkpointing to commit data to disk. The problem that we’ve seen in high IO scenearios is that it commits… from 5.1, then InnoDB‘s group commit works again. PZ: You can disable binary logging to get Group Commit back. Though this…
