… innodb_read_views_memory and innodb_descriptors_memory status variables in the Extended Show Engine InnoDB Status to improve InnoDB memory usage diagnostics. Bugs Fixed: Fix for bug #1131187 introduced a regression that could cause a memory leak if query cache was used together with InnoDB. Bug…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
…the presentation, it’s currently up and available for viewing over at percona.com. My apologies if we …performance regressions compared to 5.5, such as bug #69258, and bug #69318, and I think it might take …-grant-tables and insert a few rows into an InnoDB table, but trying to run a simple mysqlslap …
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
… upstream bug #49169 by avoiding the malloc call in the read_view_create_low() in most cases. This significantly improves InnoDB scalability on… read_view_open_now() which is another problem originally reported as upstream bug #49169. This also provides much better scalability in InnoDB high…
Post: Percona Server for MySQL 5.5.30-30.2 now available
… upstream bug #49169 by avoiding the malloc call in the read_view_create_low() in most cases. This significantly improves InnoDB scalability on… read_view_open_now() which is another problem originally reported as upstream bug #49169. This also provides much better scalability in InnoDB high…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
… is another issue in InnoDB transaction processing that notably affects MySQL performance – for every transaction InnoDB creates a read view and allocates memory… bugs: BUG#54982, BUG#49169. 2) memory allocation for read-view structure is not a direct malloc() call, but rather goes through the InnoDB heap…
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
… of InnoDB scalability is the trx_list scan on consistent read view creation. It was originally reported as a part of MySQL bug… to determine which transactions are seen in the view later. To this end, InnoDB scans trx_list (i.e. the list of… modify any data, it is irrelevant whether a consistent read view sees them or not. The main limitation is obvious: if…
Post: Heikki Tuuri answers to Innodb questions, Part II
…: My impression (from an external user of Innodb point of view) is that performance bugs don’t receive very hi priority. Yet, a… the scalability of InnoDB-5.0.30 in December 2006 with a large patch, and the ‘last’ serious bug in it was… matter the other day – choosing innodb_buffer_pool_size Q36: There have been several MySQL bugs opened about multi-core scalability (concurrent…
Post: InnoDB benchmarks
… in 5.1.12 (more info about InnoDB mutexes) Scalabilty issue, the well know bug 15815, that was fixed in 5.0…-innodb and next startup options were used: libexec/mysqld –no-defaults –user=root –innodb-buffer-pool-size=1500M –innodb-log-file-size=100M –innodb… and used queries is avaiable here: http://docs.google.com/View?docid=d7fzh8b_7dwd8m7 or on our page http://www.mysqlperformanceblog…
Post: InnoDB thread concurrency
…, optimizer) and storage engine. From storage engine’s point of view it works how (very simplified): mysql calls storage engine’s…_enter_innodb–; ENTER; } retry: if (entered_thread < innodb_thread_concurrency) { entered_threads++; thread->n_tickets_to_enter_innodb = innodb_concurrency_tickets; ENTER; } if (innodb_thread… known bug 15815 so do not think it is considered to be normal behavior. About innodb_commit_concurrency. As you saw innodb_thread…
Post: How to estimate time it takes Innodb to Recover ?
…to understand how Innodb recovery works. When Innodb recovers from logs it finds the last checkpoint time. Innodb has fuzzy …cache and so having pretty scattered updates instead updating view counter for popular movie hundreds of times per second… also may help you to catch write cache bugs…

