June 19, 2013

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

… my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings… Flight #2 Flight #2 is similar to Flight #1. MyISAM is faster than InnoDB when the database…recommended to prevent assorted security risks symbolic-links=0 innodb_stats_persistent innodb_stats_auto_update=off …

Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)

… For MySQL 5.0 and 5.1, run STOP SLAVE, CHANGE MASTER TO MASTER_HOST=” and then RESET SLAVE. For MySQL 5.5 and 5.6, run… from MySQL 5.5). If you want to know more details, please read on! MySQL 5.0/5.1 First let’s consider MySQL 5.0 and 5.1. RESET….cnf [...] master-user=rsandbox master-password=rsandbox master-host=127.0.0.1 master-port=35301 [...] Let’s disconnect the slave: mysql> stop…

Post: Virident vCache vs. FlashCache: Part 2

… benchmark tool used was sysbench 0.5 and the version of MySQL used was Percona Server 5.5.30-rel30.1-465. Each test was… spikes and produces a very constant and predictable result. vCache vs. FlashCache – the basics Once I’d determined that configuration C… within acceptable bounds. This is, however, only a hypothesis. vCache vs. FlashCache – dirty page threshold Finally, we examine the impact of…

Post: Benchmarking Percona Server TokuDB vs InnoDB

…I wanted to compare InnoDB performance vs TokuDB. I have a particular…monotonically non-decreasing ID $K=rand(0,10000) // distributed by pareto distribution …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: More on MySQL transaction descriptors optimization

… focused only on case #1. Which is the perfect case for read-only transaction optimization in MySQL 5.6, because all SELECT… a results comparison on a single-node (on the left) vs. two-node (on the right) configuration. No surprises here, 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

… rough code for this benchmark: // Identical config/code for memcached vs InnoDB $frontendOpts = array( ‘caching’ => true, ‘lifetime’ => 3600, ‘automatic_serialization’ => true… 2.33863 ms per/cmd 1.449 ms min per/cmd 7.324 ms max per/cmd 5.875 ms range per/cmd Fetching [1,000,000] items: 347181 ms total 0.347181 ms per/cmd 0.3208 ms…

Post: MySQL 6.0 vs 5.1 in TPC-H queries

…’ + 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… 5.1 and 6.0 in cold mode (I dropped OS caches by `echo 1 > /proc/sys/vm/drop_caches` and restarting mysqld) 5.1 – time 1

Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

1 – Mysql 5.5 vs 5.6 response times are in seconds (lower is better) Version Buffer Cold Run1 Run2 Run3 5.5

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

As the part of analyzing surprising MySQL 5.5 vs MySQL 5.6 performance results I’ve been looking at changes to … | 5.5.30 | 1.2.10 | | INNODB_BUFFER_POOL_INSTANCES | 1 | 8 | | QUERY_CACHE_SIZE | 0 | 1048576 | | SLOW_QUERY_LOG_FILE | /mnt/data/sandboxes/msb_5_5…_AUTH | OFF | ON | | VERSION | 5.5.30 | 5.6.10 | | INNODB_CONCURRENCY_TICKETS | 500 | 5000 | | INNODB_PURGE_THREADS | 0 | 1 | | INNODB_OPEN_FILES | 300 | 2000…

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

… lowest query time is for MySQL 5.6 which takes 0.16s less as compared to MySQL 5.5 While with join_buffer_size… MariaDB 5.5 Hash Join Disabled w/ join_buffer_size=4M & mrr_buffer_size=4M Created_tmp_disk_tables 0 0 0 0 0 0 Created_tmp_tables 1 1 1 1 1 1… is read from disk 2.2G vs 5G. However, there is one number in MariaDB 5.5 that is quite large as compared…