…. XtraDB changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write… if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete… if changed page tracking is enabled. Bug fixed #1184517. The INNODB_CHANGED_PAGES table couldn’t be queried if the log…
Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
… objects are now allocated calling calloc() directly instead of using InnoDB heap allocation. This may improve write performance for high levels… #1181887. Changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write… to indicate an incomplete result set. Bug fixed #1185040. The INNODB_CHANGED_PAGES table couldn’t be queried if the log…
Post: Percona Server for MySQL 5.5.31-30.3 now available
… has introduced innodb_read_views_memory and innodb_descriptors_memory status variables in the Extended Show Engine InnoDB Status to improve InnoDB memory usage… MySQL 5.6 version, which removed MyISAM internal temporary table mutex contention. Bug fixed #1179978. Release notes for Percona Server for…
Post: MySQL and Percona Server in LinkBench benchmark
… around mutexes and Percona Server shows much better results Configurations and how to run benchmark: [mysqld] user=root port=3306 innodb_buffer… 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_write…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
…, there is another issue in InnoDB transaction processing that notably affects MySQL performance – for every transaction InnoDB creates a read view and…, which will in turn result in contention on kernel_mutex (trx_sys->mutex in 5.6), as memory allocation occurs under that… direct malloc() call, but rather goes through the InnoDB heap layer – so InnoDB allocates heap area and then creates requested block(s…
Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the… for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262 (Alexey Kopytov). When mysqldump was used with –innodb-optimize-keys and –no…
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
… of MySQL performance that still stands in the way of InnoDB scalability is the trx_list scan on consistent read view… transactions are seen in the view later. To this end, InnoDB scans trx_list (i.e. the list of currently open… for MySQL scalability? The scan is performed under kernel_mutex (or trx_sys->mutex in 5.6) and that is one of…
Post: Percona Server for MySQL 5.5.30-30.2 now available
… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the… for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262 (Alexey Kopytov). When mysqldump was used with –innodb-optimize-keys and –no…
Post: More on MySQL transaction descriptors optimization
… optimization in MySQL 5.6 virtually eliminates contention on the mutex protecting the list of transactions, its applicability is quite limited…_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…
Post: Webinar: MySQL 5.6 Performance Schema
… temporary tables and external sorts Excessive internal mutex contention Slow queries due to waits on InnoDB locks and Meta Data locks Interested…

