May 26, 2012

Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact

… in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a… optimizer enhancement Index Condition Pushdown (ICP). Its available in both MySQL 5.6 and MariaDB 5.5 Now let’s take… such as range scans, where index parts after the part on which range condition is applied cannot be used for filtering…

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

on to the benchmarks, to see the difference in numbers. 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… following changes were made on MySQL 5.6 config: optimizer_switch=’index_condition_pushdown=off’ optimizer_switch=’mrr=on‘ optimizer_switch=’mrr_cost…

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

… the purpose of this benchmark, I have used TPC-H Query #10 and ran it on TPC-H dataset (InnoDB tables) with a Scale Factor…_sort_keys=on‘ (only on MariaDB 5.5) optimizer_switch=’mrr_cost_based=off’ read_rnd_buffer_size=4M (only on MySQL 5.6) mrr_buffer_size=4M (only on MariaDB 5.5) We have turned off…

Post: MySQL Optimizer team comments on TPC-H Results

MySQL optimizer team and Timur – both of them expressed concern with TPC-H run results I posted and notes about little gains in MySQL… reason ? Why TPC-H queries are not targeted ? The reason is MySQL Optimizer Team did not have the goal of optimizing TPC-H queries or… it into final MySQL 6.0 release. Summary: Poor MySQL 6.0 performance on TPC-H queries does NOT mean to quantify MySQL Optimizer Team work…

Post: TPC-H Run on MySQL 5.1 and 6.0

We were doing MySQL Performance evaluation on TPC-H queries for the client and they kindly allowed us to … it in his MySQL 5.1 vs 6.0 in TPC-H Queries post As a Summary: We can see MySQL capabilities to run complex analytics queries, in particular those presented in TPC-H

Post: MySQL 6.0 vs 5.1 in TPC-H queries

… I played with queries from TPC-H benchmarks, particularly comparing MySQL 6.0.4-alpha with 5.1. MySQL 6.0 is interesting here… new changes in optimizer, which should affect execution plan of TPC-H queries. In reality only two queries (from 22) have significantly… we have on this server. This is because of Random I/O we had during execution of query, as MySQL used index…

Comment: TPC-H Run on MySQL 5.1 and 6.0

Hi. I’m trying to execute the tpc-h queries on a mysql 5.0.27 system. Some of my results are somewhat … have a look at your create table scripts for the tpc-h standard ? Thanks in advance.

Comment: The performance effects of new patches

… standard MySQL, as it is less tested. We are going to recommend this release to customers who experience scaling problem, especially on… this moment. We are testing it on our production system, on TPC-C, TPC-E, TPC-H emulation workloads, on intensive sysbench benchmarks and we have no…

Comment: TPC-H Run on MySQL 5.1 and 6.0

… Kickfire published 100GB TPC-H results (audited) where none of the queries took more than 37 SECONDS – so for example on Q1 it’s 100 TIMES faster than result above (http://www.tpc.org/results/individual_results/Kickfire/Kickfire_2300_ES_TPCH_100G_041408.pdf) it appears MySQL/Sun have some…

Post: Star Schema Bechmark: InfoBright, InfiniDB and LucidDB

…/). Addressing these issues, I took Star Schema Benchmark, which is TPC-H modification, and tried run queries against InfoBright, InfiniDB, LucidDB and…. You can see more details on InfiniDB scalability on InfiniDB’s blog http://infinidb.org/infinidb-blog/mysql-parallel-query-processing-of-ssb…