… the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one… Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take a look briefly at what… WHERE condition defined as: l_partkey = x and l_quantity >= 1 and l_quantity = 1 and l_quantity
Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact
March 12, 2012 By 12 Comments
Post: MySQL QA Team Benchmarks for MySQL 5.1.30
December 13, 2008 By 12 Comments
… have seen MySQL QA Team has published their benchmarks for MySQL 5.0.72 and 5.1.30. It is interesting to compare with results… the graphs provided in these benchmarks and see what value is best for MySQL 5.1 and for MySQL 5.0 respectively ? Both versions do… for MySQL 5.0 to see if they are possible to be reclaimed. Finally – if I would be doing QA, and benchmarks as…
Post: MySQL 6.0 vs 5.1 in TPC-H queries
March 25, 2008 By 17 Comments
… played with queries from TPC-H benchmarks, particularly comparing MySQL 6.0.4-alpha with 5.1. MySQL 6.0 is interesting here, as there…’ + interval ‘1‘ year AND l_discount BETWEEN 0.09 – 0.01 AND 0.09 + 0.01 AND l_quantity < 24; with execution plain (in 5.1) +—-+————-+———-+——-+—————+—————+———+——+———+————-+ | id…
Post: MySQL 5.5.8 and Percona Server on Fast Flash card (Virident tachIOn)
December 21, 2010 By 11 Comments
…flush_neighbor_pages=0 innodb_adaptive_checkpoint=keep_average innodb_read_ahead=none For MySQL 5.5.8, I… results, config, and script are in our Benchmarks Wiki. Here are the graphs: 13G innodb_… 1.29x 52GB: MySQL 5.5.8 – 71,774 NOTPM, Percona Server – 88,792 NOTPM, advantage: 1.23x 144GB: MySQL 5.5….
Post: InnoDB benchmarks
January 3, 2007 By 15 Comments
…, so I ran benchmark to check new results and also compare overall performance of InnoDB in 5.0 and 5.1 before and after fixes… was fixed in 5.0.30 and 5.1.14. So I took for tests: 5.0.27, the release with both problems 5.0.32-bk (snapshot… 5.0.27) and after fix (5.0.30/5.1.14 and later) The fix of 15815 shows good results: in 5.0.32 (comparing to 5.0.27…
Post: TPC-H Run on MySQL 5.1 and 6.0
April 10, 2008 By 16 Comments
… 6.0 time divided by MySQL 5.1 time so if it is less than 1 MySQL 6.0 is faster if more than 1 slower: Query MySQL 5.0.23 MySQL 6.0… presented in TPC-H benchmark are still subpar even with changes which are currently seen in MySQL 6.0 tree. There is…
Post: MySQL 5.5.8 - in search of stability
January 3, 2011 By 11 Comments
… throughput in MySQL 5.5.8. Let’s see what we can do with them. Article [1]Â also … for each run, I will show different graphs: benchmark throughput – This is New Order Transactions per 10 … we disable doublewrite; that is, set innodb_doublewrite=0. Now, although throughput is not a perfect line,…
Post: DROP TABLE and stalls: Lazy Drop Table in Percona Server and the new fixes in MySQL
June 22, 2012 By 33 Comments
…=sbtest_20m –max-time=900 –num-threads=8 –max-requests=0 run Note that the tables that were being dropped had… 5.5.23 DROP TABLE implementation is MySQL 5.5.15, the version of MySQL used for benchmarking the new DROP TABLE implementation is MySQL 5.5.24, and the version of Percona Server used for benchmarking Lazy Drop Table is Percona Server 5.5.24 (innodb_lazy_drop_table=1…
Post: Performance improvements in Percona 5.0.83 and XtraDB
July 14, 2009 By 27 Comments
… benchmark, results during run: And averaged final result: As you see XtraDB, 5.0.83-percona and MySQL 5.4 are almost equal, leaving 5.0… topic for another benchmark. And now IO-bound results Again you can see that XtraDB, 5.0.83-percona and 5.4 are almost… choose XtraDB if 5.4 has the same performance, let me refresh: – XtraDB is based on InnoDB plugin 1.0.3, with all…
Post: table_cache negative scalability
November 16, 2009 By 23 Comments
… note significant writes to the disk during this read-only benchmark. Why ? Because for MyISAM tables table header has to be… MySQL 5.0.85. So the problem is not fixed in MySQL 5.1, lets see how MySQL 5.4 behaves. MySQL 5.4.2 MySQL 5… compare apples to apples. It performs same as MySQL 5.0 and MySQL 5.1 with small table cache. With table_open_cache increased…
