…the Star Schema Benchmark. In my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10,… Flight #2 Flight #2 is similar to Flight #1. MyISAM is faster than InnoDB when the …recommended to prevent assorted security risks symbolic-links=0 innodb_stats_persistent innodb_stats_auto_update=off …
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
… this benchmark, can be found here. We decided to run this benchmark for MySQL Server 5.5.30, 5.6.11 and Percona Server 5.5.30… Server shows much better results Configurations and how to run benchmark: [mysqld] user=root port=3306 innodb_buffer_pool_size = 30G… 10x dataset: ./bin/linkbench -D dbid=linkdb -D host=127.0.0.1 -D user=root -D port=3306 -D password= -D maxid1…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
… 5.5.30-30.2 and a followup by Dimitri Kravchuk, we have received a large number of questions on why the benchmark… well, so we tried to answer that question by retrying benchmarks on various combinations of hardware and dataset sizes, including the…(*) from sbtest$i WHERE k like ‘%0%’ SysBench-0.5/lua: POINT_SELECT QPS test sysbench –num-threads=<1..1024> –test=oltp.lua –oltp…
Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer
March 29, 2013 By 10 Comments
…: http://dev.mysql.com/doc/refman/5.6/en/innodb-memcached-setup.html As a quick benchmark, I ran some batches of fetch and store against both a standard memcached instance and a minimally tuned MySQL 5… MySQL Select (same table): Fetching [1,000,000] items: 441573 ms total 0.441573 ms per/cmd 0.4327 ms min per/cmd…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
… the benchmarks on both systems. The benchmark tool used was sysbench 0.5 and the version of MySQL used was Percona Server 5.5.30-rel30.1… vCache can be declared the clear winner. Base MySQL & Benchmark Configuration All benchmarks were conducted with the following: sysbench –num-threads=32…
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
…monotonically non-decreasing ID $K=rand(0,10000) // distributed by pareto distribution BEGIN… if you want to repeat this benchmark, the sysbench code is on …interleave malloc-lib=/usr/local/Percona-Server-5.5.30-rel30.2-500.Linux….file_size = 10G myisam_repair_threads = 1 myisam_recover socket=/var/lib…
Post: Death match! EBS versus SSD price, performance, and QoS
February 21, 2011 By 55 Comments
…do benchmarks, but that would not be interesting — we already know that benchmarks …0.0 0.0 0.0 0.0 0.0 2.5 0% 0 23.2 sdi2 0.0 0.0 0.0 0.0 0.0 2.0 0% 0 23.2 sdj5 0.0 0.0 0.0 0.0 0.0 1.0 0% 0 23.2 sdi4 0.0 0.0 0.0 0.1 0.0 2.2 1% 0 23.2 sdi3 0.0 0.0 0.0 0.1 0.0 2.5 1% 0 23.2 sdj3 0.0 0.0 0.0 0.1 0.0…
Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5
March 21, 2012 By 10 Comments
… of MySQL 5.5 and ~5 hours in case of MySQL 5.6 and MariaDB 5.5. Note that query cache is disabled during these benchmark runs… benchmark on IO bound workload, mentioned above. Counter Name MySQL 5.5 MySQL 5.6 MySQL 5.6 w/ read_rnd_bufer_size=4M MariaDB 5.5 MariaDB 5.5 w/ mrr_buffer_size=4M Created_tmp_disk_tables 1 1 1 1 1 Created_tmp_tables 1 1 1 1 1 Handler_mrr_init N/A 0 0 1 1 Handler…
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: A case for MariaDB's Hash Joins
May 31, 2012 By Leave a Comment
… be running my benchmarks on the newer MariaDB 5.5. Overview Hash Join is a new algorithm introduced in MariaDB 5.3/5.5 that can…. The benchmarks compare Block Nested Loop (BNL) Join of MySQL 5.5.24, Batched Key Access (BKA) Join of MySQL 5.6.5 and Block…=O_DIRECT query_cache_size=0 query_cache_type=0 MySQL 5.6.5 Configuration innodb_file_per_table=1 innodb_file_format=barracuda innodb…
