… is long over, but still the tool serves well for benchmark purposes. OK, let’s start off with the configuration details… used: ## InnoDB options innodb_buffer_pool_size = 55G innodb_log_file_size = 1G innodb_log_files_in_group = 4 innodb_buffer_pool_instances = 4 innodb_adaptive… the EC2 instance and MySQL. Now as far as the benchmark itself is concerned, I made no code changes to iiBench…
Post: Testing STEC SSD MACH16 200GB SLC
… IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and… suitable to work with MySQL. I will publish sysbench oltp benchmarks running MySQL on RAID10 over 4 STEC MACH16 cards. If… talk – you are welcome to join the webinar. Disclaimer: This benchmark is done as part of consulting work for STEC, but…
Post: Testing Samsung SSD SATA 256GB 830 - not all SSD created equal
… use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I… IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and… random write case (8 async IO threads): It seems that InnoDB is not alone with its flashing problems. You can see…
Comment: Benchmarking single-row insert performance on Amazon EC2
Justin, I would be doing another benchmark and use ‘innodb_ibuf_accel_rate’ together with tuning other IO related parameters that I can tune to good affect, and I will post my results.
Comment: Benchmarking single-row insert performance on Amazon EC2
This benchmark doesn’t test the IO performance of EBS though as you’re not flushing to disks on each commit. What numbers do you get when you set innodb_flush_log_at_trx_commit to 1?
Comment: MySQL on Amazon RDS part 1: insert performance
I see no improvement from RDS with innodb_flush_log_at_trx_commit set to 2 or 0. My benchmarks have the same results, regardless of the setting. Does RDS fools the flush in some way or has the setting disabled somehow?
Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5
…. Benchmark results For the purpose of this benchmark, I have used TPC-H Query #10 and ran it on TPC-H dataset (InnoDB… fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer pool size is set to 6G and… workload is IO bound. For the purpose of benchmarking IO bound workload, the InnoDB buffer pool size is set to 1G and…
Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact
… MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in the same way…
Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5
…. Benchmark results For the purpose of this benchmark, I have used TPC-H Query #3 and ran it on TPC-H dataset (InnoDB tables) with a Scale Factor of 2 (InnoDB dataset size ~5G). Note that query cache is disabled during these benchmark runs… fits entirely in memory. For the purpose of benchmarking in-memory workload, the InnoDB buffer pool size is set to 6G and…
Post: ext4 vs xfs on SSD
… one more point to consider. Starting the MySQL 5.1 + InnoDB-plugin and later MySQL 5.5 (or equally Percona Server… MiB/sec It corresponds to results I see running MySQL benchmarks (to be published later) on ext4 vs xfs. Actually amount… 20% better throughput. I am still going to run more benchmark to get better picture. The script for tests: for size…

