…5.5.30-30.2 and a followup by Dimitri Kravchuk, we have received a large number of questions on why the benchmark… tests Percona Server scalability is somewhere in between of MySQL 5.5 and MySQL 5.6. In order…count(*) from sbtest$i WHERE k like ‘%0%’ SysBench-0.5/lua: POINT_SELECT QPS test sysbench –…
Post: MySQL 5.0, 5.1 and Innodb Plugin CPU Efficiency
December 3, 2008 By 15 Comments
We’ve recently done benchmarks comparing different MySQL versions in terms of their CPU efficiently … than MySQL 5.0 with two cores and just 2% slower with 8 cores, thus showing a bit better scalability. MySQL 5.1 plugin (compiled in) is further 3% slower compared to MySQL 5.1 with 2 cores…
Post: MySQL/Innodb scalability tests after fix
January 3, 2007 By 1 Comment
… too large to only map it to Innodb scalability patch. 2) Speedup for 5.0.32 for large number of CPUs (2x quad… larger than for 5.0.20 – some 630 vs 540 tps. 4) The bad news are – we still have massive scalability drop with… looking at this benchmark (it can be and will be different in other benchmarks) we can see MySQL scalability problem with high number…
Post: MySQL 5.5.8 and Percona Server: being adaptive
December 20, 2010 By 25 Comments
…see, MySQL 5.5.8 comes with great improvements and scalability fixes. Adding up all the new features…even before that, in percona-patches builds for 5.0), we added adaptive checkpoint algorithms, and later … 5.5 code line. The answer: Yes, we are. My benchmarks here are based on Percona Server 5.5.7….
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… page http://www.mysqlperformanceblog.com/files/benchmarks/innodb_scale.html (Note: This benchmark is synthetic micro benchmarks focusing on particular simple data access… scalability problem, but the main goal was the comparison of overall performance of InnoDB before fix (in 5.0.27) and after fix (5.0…
Post: Watch out for Marketing benchmarks
August 23, 2006 By 7 Comments
… at MySQL 5.0 Benchmarks Whitepaper and guess which type is this ? You can also compare it to my MySQL Performance 5.0 vs 4….1 vs 5.0 benchmarks which were done only benchmarks which show MySQL 5.0 is faster were selected and bunch of other benchmarks which show 5.0 is… are performance bugs, some of them as Innodb Scalability were known long before MySQL 5.0 was stable but were not fixed, others…
Post: table_cache negative scalability
November 16, 2009 By 23 Comments
…LRU for cache management is classics and there are scalable algorithms to deal with it. I would …writes to the disk during this read-only benchmark. Why ? Because for MyISAM tables table header has…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…
Post: MySQL and PostgreSQL SpecJAppServer benchmark results
July 25, 2007 By 13 Comments
…, PostgreSQL benchmarks use Sun Fire X4200 M2 available in September 2006, using AMD Opteron 2220 SE. We can see some 5% difference… big issue is using MySQL 5.0.27 which has Innodb scalability issues, which were a lot improved in 5.0.37 which I’d expect to show significant gains. This is not to mention specific tuning for Benchmark which…
Post: Call for opinions: Do we need MySQL 5.0 with MySQL 5.4 performance
April 29, 2009 By 12 Comments
… workload, which consists of the queries running just fine on 5.0. 5.4 especially introduces optimizer changes which besides positive impact for… and fast index build. Innodb plugin 1.0.3 got some Google changes for CPU scalability but not IO patches. I expected… of default Innodb in MySQL 5.4 will this ever going to happen ? Looking at initial benchmarks I’m very impressed with…
Post: mysql-proxy, urgh performance and scalability ?
June 9, 2009 By 44 Comments
… going to be active developer of this project and scripting benchmarks). I took lp:sysbench with LUA script oltp_complex_ro… (in transactions per second, more is better) ThreadsMySQL-5.0.77MySQL-proxy+MySQL-5.0.77 1 660.02 349.86 2 1158.66… per-request statistics: min: 1.31ms avg: 1.51ms max: 5.30ms approx. 95 percentile: 1.56ms Proxy+MySQL per-request…
