Evgeny Stanilovsky created IGNITE-29243:
-------------------------------------------
Summary: Calcite. Reduce planning time
Key: IGNITE-29243
URL: https://issues.apache.org/jira/browse/IGNITE-29243
Project: Ignite
Issue Type: Improvement
Components: sql
Affects Versions: 2.19
Reporter: Evgeny Stanilovsky
Despite of [1] dramatically improve execution time for some queries, it also
reduce a bit some 'cold', 'not cached' or - other words - fair, without cache
looks up queries execution. It always slower than appropriate h2, seems it need
to be reduced, ideally - aligned with h2.
PR:
TpchBenchmark.cold CALCITE 1 0.01 ss 579.535
ms/op
TpchBenchmark.cold CALCITE 2 0.01 ss 1267.930
ms/op
TpchBenchmark.cold CALCITE 3 0.01 ss 1709.587
ms/op
TpchBenchmark.cold CALCITE 4 0.01 ss 642.988
ms/op
TpchBenchmark.cold CALCITE 6 0.01 ss 287.134
ms/op
TpchBenchmark.cold CALCITE 7 0.01 ss 1754.577
ms/op
master:
TpchBenchmark.cold CALCITE 1 0.01 ss 522.240
ms/op
TpchBenchmark.cold CALCITE 2 0.01 ss 965.328
ms/op
TpchBenchmark.cold CALCITE 3 0.01 ss 1305.522
ms/op
TpchBenchmark.cold CALCITE 4 0.01 ss 661.892
ms/op
TpchBenchmark.cold CALCITE 6 0.01 ss 358.714
ms/op
TpchBenchmark.cold CALCITE 7 0.01 ss 923.471
ms/op
h2:
TpchBenchmark.cold H2 1 0.01 ss 295.369
ms/op
TpchBenchmark.cold H2 2 0.01 ss 271.722
ms/op
TpchBenchmark.cold H2 3 0.01 ss 362.651
ms/op
TpchBenchmark.cold H2 4 0.01 ss 117.404
ms/op
TpchBenchmark.cold H2 6 0.01 ss 148.289
ms/op
TpchBenchmark.cold H2 7 0.01 ss 732.207
ms/op
[1] https://issues.apache.org/jira/browse/IGNITE-28899
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
