June 18, 2013

Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2

… a snapshot of the transaction states to determine which transactions are seen in the view later. To this end, InnoDB scans trx_list (i.e. the list of currently open transactions) and copies IDs of transactions that have not… the REPEATABLE_READ isolation level, the snapshot is created on the first SELECT for each transaction. For lower isolation levels it is created…

Post: Innodb undo segment size and transaction isolation

… does transaction isolation affects purging ? Innodb is smart and trying to purge data as soon as possible. In default (REPEATABLE-READ) mode Innodb has… this case anyway, even if you set transaction isolation to lowest READ-UNCOMMITTED level Innodb will not purge the rows from undo space…

Post: Differences between READ-COMMITTED and REPEATABLE-READ transaction isolation levels

… we are now holding only one lock. In all transaction isolation levels InnoDB creates locks over every index entry scanned. The difference between… … FOR UPDATE. Useful links Percona Training – InnoDB internals day covers MVCC and locking in detail The SET TRANSACTION ISOLATION LEVEL MySQL manual page

Post: InnoDB's gap locks

… write queries, in spite of your chosen transaction isolation level (considering only the two most common isolation levels, REPEATABLE READ and READ COMMITTED…? Is possible to detect those gap locks using SHOW ENGINE INNODB STATUS: —TRANSACTION 72C, ACTIVE 755 sec 4 lock struct(s), heap…

Post: Innodb Performance Optimization Basics

… especially on a lot of short write transactions. innodb_thread_concurrency=8 Even with current Innodb Scalability Fixes having limited concurrency helps. The… can run in READ-COMMITED isolation mode – if it does – set it to be default as transaction-isolation=READ-COMMITTED. This option has…

Post: Heikki Tuuri Innodb answers - Part I

…: How do you assess current state of Innodb scalability with multiple threads and multiple concurrent transactions ? HT: The scalability in my opinion… implemented in 5.1: if you set the transaction isolation level READ COMMITTED, then InnoDB normally does not lock the ‘gaps’, and it… not remove that serialization. MySQL’s binlog and InnoDB‘s log must have the transactions in the same order, for a recovery…

Post: XtraDB/InnoDB CPU bound benchmarks on 24cores server

…_group=2 innodb_log_file_size=512M innodb_status_file=0 innodb_thread_concurrency=0 innodb_io_capacity=1000 innodb_write_io_threads = 16 innodb_read… thread_concurrency=16 thread_stack=196K tmp_table_size=64M transaction_isolation=REPEATABLE-READ local-infile=1 At first I tried sysbench…

Post: MVCC: Transaction IDs, Log Sequence numbers and Snapshots

… bit. This is general explanation, it does not corresponds to Innodb in particular and some implementation can be different but I… consider transaction 101 which is running in REPEATABLE-READ isolation mode and which was started before transaction 100 have committed. In such case transaction