June 19, 2013

Post: The small improvements of MySQL 5.6: Duplicate Index Detection

performance

Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency

… adaptive hash index is improving performance of InnoDB significantly during the hot run, as hash indexes are faster than a b-tree index. Also… using MyISAM for everything!. MyISAM may be good for raw performance, but there are limitations which MyISAM imposes that are difficult… operations and is not ACID compliant. MyISAM and InnoDB may perform differently under concurrency, which this benchmark does not cover. I…

Post: MySQL Query Patterns, Optimized - Webinar questions followup

… subqueries) and we saw in my presentation that sometimes these perform worse and sometimes better than another equivalent solution. If you… solution for randomly choosing rows involves some compromise, either of performance, or of accuracy of randomness.  The ORDER BY RAND() solution… okay because each correlation name (k1, k2, k3) is an index lookup.  Look at the EXPLAIN output — it accesses these first…

Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL

…2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack on other accounts efficiently. … the User Statistics tables in INFORMATION_SCHEMA (CLIENT_STATISTICS, INDEX_STATISTICS, TABLE_STATISTICS, THREAD_STATISTICS, and USER_STATISTICS) led …

Post: Percona Server 5.6.11-60.3 first Release Candidate now available

… instead of using InnoDB heap allocation. This may improve write performance for high levels of concurrency. Bug fixed #1185686. Under very… performance on write-intensive workloads. Bug fixed #1171699. Incorrect schema definition for the User Statistics tables in INFORMATION_SCHEMA (CLIENT_STATISTICS, INDEX

Post: More on MySQL transaction descriptors optimization

… variation, e.g. in the first two cases Percona Server performance is even slightly ahead of MySQL 5.6.10, but…_connections=5000 table_open_cache=5000 query_cache_type=OFF performance_schema=0 warmup To warmup server and load data and…-test-mode=nontrx –oltp-read-only=off –oltp-index-updates=0 –oltp-non-index-updates=0 run POINT_SELECT + UPDATE QPS test…

Post: MySQL and Percona Server in LinkBench benchmark

… MySQL performs quite well, though we can see small performance drop in MySQL 5.6. In IO-bound cases MySQL still has performance…-cache=1000 query_cache_size=0 query_cache_type=0 performance_schema=0 #56only loose-innodb_flush_neighbors=0 loose-metadata…-innodb_io_capacity_max = 15000 #Percona only innodb_adaptive_hash_index_partitions=8 innodb_buffer_pool_instances=1 innodb_adaptive_flushing…

Post: Announcing Percona XtraBackup 2.1.1 GA

…of threads started by XtraBackup when rebuilding secondary indexes on innobackupex –apply-log –rebuild-indexes. This allows parallel processing of individual … Percona XtraBackup can use XtraDB changed page tracking feature to perform the Incremental Backups now. Bugs Fixed: innobackupex is using …

Comment: Benchmarking Percona Server TokuDB vs InnoDB

Vadim, Thanks for a great performance report. Not sure I understand why InnoDB used 210 GB … estimates? 234M * (200 + 20) for PK index + 234M * (12 + 7) * 1.5 for fragmented secondary index + 234M * (12 + 20) * 1.5 for…/3 full So my guess is: * 50G for PK index * 6G for secondary index on base table * 11G for sbtest_r10 * much…

Comment: Benchmarking Percona Server TokuDB vs InnoDB

The main performance win of TokuDB is indexes. If you add multiple multi-column indexes the difference with InnoDB will be even more notable. Also it allows multiple clustering indexes… and 4.x). It really shines on large tables and index scan like queries.