June 19, 2013

Post: Identifying the load with the help of pt-query-digest and Percona Server

and the query execution plan used by MySQL. The end result might be that you end up limiting the number of resultstotal min max avg 95% stddev median # ============ === ======= ======= ======= ======= ======= ======= ======= # Count

Post: Analyzing air traffic performance with InfoBright and MonetDB

And total load time is 8836 sec (2.45h). The size of database after load is 1.6G which is impressive and givecount(*) FROM ontime;. Both InforBritgh and MonetDB executes it immediately with result 117023290 rows Now some random queries I tried again both databases: -Q1: Count

Post: Flexviews - part 3 - improving query performance using materialized views

total_items’); CALL flexviews.add_expr(@mvid,’SUM’,'price * quantity’,’total_price’); CALL flexviews.add_expr(@mvid,’COUNT‘,’*',’total

Post: A case for MariaDB's Hash Joins

results of executing benchmarks for different queries and explain the results…/3 rows. And so both the build and probe phase…, which means the total dataset size is 4…s_nationkey, l_shipmode, count(*) FROM supplier INNER JOIN … that Hash Join gives a lot of …we have a limited set of rows in the supplier …

Post: Four ways to optimize paginated displays

results, maybe you can fetch 501 and if the 501st row exists, display “more than 500 results found.” Don’t show the total countresult than you want to display — for example, fetch 21 rows and display only 20. If there’s a 21st row

Post: InnoDB compression woes

gives about 6GB of data per table (uncompressed) and 96GB of data in total. ./sysbench –test=tests/db/parallel_prepare.lua –oltp-tables-countResults: Load time for regular tables: 19693 sec, for compressed tables: 38278 sec. Compressed tables are create as: ROW