June 18, 2013

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

… the InnoDB storage engine.  In my testing I discovered that innodb_old_blocks_time had an effect on performance of the benchmark.  There… presents some unique challenge to the database optimizer. The SSB benchmark consists of four sets of queries. Each set is known… and is not ACID compliant. MyISAM and InnoDB may perform differently under concurrency, which this benchmark does not cover. I will make…

Comment: Benchmarking Percona Server TokuDB vs InnoDB

Hi Vadim, I can confirm the steady downfall of InnoDB throughput down to ~1500 insert/sec (and counting) while TokuDB … around 100Million rows using Tokutek’s iibench.py for the benchmark on a 2-way Supermicro server with 2 Xeon X5650…

Post: MySQL and Percona Server in LinkBench benchmark

Around month ago Facebook has announced the Linkbench benchmark that models the social graph OLTP workload. Sources, along with … how to setup and run this benchmark, can be found here. We decided to run this benchmark for MySQL Server 5.5… to run benchmark: [mysqld] user=root port=3306 innodb_buffer_pool_size = 30G innodb_flush_method = O_DIRECT innodb_log_file_size = 2000M innodb_log…

Post: Benchmarking Percona Server TokuDB vs InnoDB

… measure that also. And, if you want to repeat this benchmark, the sysbench code is on Launchpad lp:~vadim-tk/sysbench…_average innodb_file_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush… #####plugin options innodb_read_io_threads = 16 innodb_write_io_threads = 4 innodb_io_capacity = 4000 innodb_use_native_aio=0 #not innodb options (fixed…

Post: Virident vCache vs. FlashCache: Part 2

…can be declared the clear winner. Base MySQL & Benchmark Configuration All benchmarks were conducted with the following: sysbench ­­–num­-threads…fixed innodb options innodb_file_format = barracuda innodb_buffer_pool_size = 4G innodb_file_per_table = true innodb_data_file_path = ibdata1:100M innodb_…

Post: More on MySQL transaction descriptors optimization

… have received a large number of questions on why the benchmark results in both posts look rather different. We were curious… well, so we tried to answer that question by retrying benchmarks on various combinations of hardware and dataset sizes, including the…_commit = 2 innodb_flush_method = O_DIRECT innodb_log_buffer_size = 16M innodb_buffer_pool_size = 52G innodb_log_file_size = 2000M innodb_log_files…

Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer

….mysql.com/doc/refman/5.6/en/innodb-memcached-setup.html As a quick benchmark, I ran some batches of fetch and… Here is the rough code for this benchmark: // Identical config/code for memcached vs InnoDB $frontendOpts = array( ‘caching’ => true, ‘lifetime’ => 3600, ‘automatic…(“key_$i”); } } $totalTimeFetch = $timer->stop(); $avgTimeFetch = $totalTimeFetch / 1000000; While this benchmark doesn’t show any multi-threading or other advanced operation…

Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2

… of MySQL performance that still stands in the way of InnoDB scalability is the trx_list scan on consistent read view… take a look at the following benchmark: This is the so-called QPS-mode POINT_SELECT benchmark, i.e. all queries are… Server’s scalability is the same as in the previous benchmark. The overhead of maintaining the descriptors array is negligible as…

Post: Virident vCache vs. FlashCache: Part 1

… to conduct some benchmarks for the use case where the MySQL working set is significantly larger than the InnoDB buffer pool (thus… this series, wherein we’ll take a look at some benchmarks. There’s no razor-thin margin of victory for either…

Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2

…, there is another issue in InnoDB transaction processing that notably affects MySQL performance – for every transaction InnoDB creates a read view and… direct malloc() call, but rather goes through the InnoDB heap layer – so InnoDB allocates heap area and then creates requested block(s…