… the CVE-2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password …page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting … file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to …
Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL
June 10, 2013 By 3 Comments
Post: Percona Server for MySQL 5.5.31-30.3 now available
May 24, 2013 By Leave a Comment
… InnoDB. Bug fixed #1170103. Fixed the RPM packaging regression that was introduced with the fix for bug #710799. This regression caused mysql… the MySQL 5.6 version, which removed MyISAM internal temporary table mutex contention. Bug fixed #1179978. Release notes for Percona Server for MySQL…
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
…” align=”alignright” width=”247″] Percona Server for MySQL version 5.6.11-60.3[/caption]… allocated calling calloc() directly instead of using InnoDB heap allocation. This may improve write performance … page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting…
Post: Percona Server for MySQL 5.5.30-30.2 now available
April 10, 2013 By 10 Comments
… MySQL has fixed a number of performance bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb… MySQL 5.6 the fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262 (Alexey Kopytov). When mysqldump was used with –innodb…
Post: Webinar: MySQL 5.6 Performance Schema
May 13, 2013 By 5 Comments
….m. Pacific, I’ll be leading a Webinar titled, “Using MySQL 5.6 Performance Schema to Troubleshoot Typical Workload Bottlenecks.” In… Schema, focusing on new features that have been added in MySQL 5.6, go over the configuration and spend most time… temporary tables and external sorts Excessive internal mutex contention Slow queries due to waits on InnoDB locks and Meta Data locks Interested…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
… a chart with top mutexes for each server at 64 threads: For MySQL 5.5.30 top mutex is &doublewrite->mutex: trx0sys.c:196…_instances=256 innodb_buffer_pool_instances=16 # MySQL 5.5 and 5.6 loose-innodb_io_capacity_max = 15000 #Percona only innodb_adaptive_hash_index_partitions=8 innodb_buffer_pool…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
April 15, 2013 By
…, there is another issue in InnoDB transaction processing that notably affects MySQL performance – for every transaction InnoDB creates a read view and allocates…, 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
April 24, 2013 By Leave a Comment
… MySQL has fixed a number of performance bugs. (Alexey Kopytov) Drop table performance feature has been removed and its controlling variable innodb… MySQL 5.6 the fix for unnecessary log_flush_order_mutex acquisition. Bug fixed #1163262 (Alexey Kopytov). When mysqldump was used with –innodb…
Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2
April 12, 2013 By 3 Comments
One major problem in terms of MySQL performance that still stands in the way of InnoDB scalability is the trx_list scan on consistent read view creation. It was originally reported as a part of MySQL… that a major problem for MySQL scalability? The scan is performed under kernel_mutex (or trx_sys->mutex in 5.6) and that…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
… the read-only transactions optimization in MySQL 5.6 virtually eliminates contention on the mutex protecting the list of transactions, …120 –max-requests=0 –percentile=99 –mysql-user=root –mysql-db=sbtest8t1M –mysql-table-engine=INNODB –mysql-socket=/tmp/mysql.sock –oltp-point-selects=1 –…
