TPC-H & Cost-Performance Relationship

Comparing Oracle DB, Exadata, EnterpriseDB and Tibero Database

4 Solutions = 4 different User Experience + ROI

The Long Run means, how long would you go with your solution with a given fixed budget. What would be the performance expected?

Findings

  • Storage “Predicate Filtering” is very important to improve the overall performance of the data access.
    • For any big table, the importance of Storage Predicate Filtering is notable.
    • The difference of having and not having Predicate Filtering is huge while comparing EDB and Tibero.

 

  • The backup utility “bart” or “pg_dump” is lightyears behind the quality given by impdp (Oracle) or tbImport (Tibero)

 

  • SELECT, UPDATE or DELETE are the base of any application, that’s why, optimizing these operations can provide a very positive user experience.

Download the dump files ... Reproduce this test yourself ... Test your own server and compare ...

Available for:

  • Oracle Database 12c, 18c and 19c.
  • EDB Postgres Advanced Server 12
  • Tibero 6
Check the queries
Click here to see the TPC-H SQL queries executed

The queries (Q1-4 & U1 & D1)

set timing ON time on echo on
set autot TRACE
-- Before each query, in Oracle or Tibero run: 
alter system flush shared_pool;
alter system flush buffer_cache;
exec DBMS_RESULT_CACHE.FLUSH();
select count(1)
from tpch.h_lineitem
where l_shipdate >= date '1996-01-01';
select count(o_orderkey)
from tpch.h_order
where o_totalprice between 100000 and 200000;
select sum(l_extendedprice * l_discount) as revenue
from tpch.h_lineitem
where l_shipdate >= date '1996-01-01'
and l_shipdate < date '1996-01-01' + interval '1' year
and l_discount between 0.06 - 0.01
and 0.06 + 0.01 and l_quantity < 24;
select sum(l_extendedprice * (1 - l_discount)) as promo_revenue
from tpch.h_lineitem, tpch.h_part
where l_partkey = p_partkey
and l_shipdate >= date '1994-09-01'
and l_shipdate < date '1994-09-01' + interval '1' month;
UPDATE tpch.h_lineitem
SET l_discount = 0.22
WHERE l_discount = 0.02;
rollback; -- rollback time should be considered separately.
DELETE FROM tpch.h_lineitem
where l_shipdate <= date '1996-01-01'
and l_shipdate > date '1992-01-01' + interval '1' year;
rollback; -- rollback time should be considered separately.

No time to test?

We work with automation.

We can prepare the test environment on a click for you.

You just need to let us know with this form and we will launch it.

 

Interactive Hands-on LIVE DEMO?

15 + 14 =

Reproduce instructions not yet published 🙂

Contact us if you are interested to reproduce the tests above.

How to reproduce the test in:

Estimated dedication: 30 min

Estimated load time: Between 15 minutes to 3 hours depending of your server speed and PARALLEL setting.

Estimated dedication: At least hours to days.

Estimated load time: Hours to 4-5 days.

Instructions

Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.

Estimated dedication: 30 min

Estimated load time: At least 15 minutes to 2 hours depending of your server and P_DPL (PARALLEL) setting. DPL = Direct Path Loading

Instructions

Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.