[CALCITE-7417] Add a large plan benchmark for HepPlanner#4796
[CALCITE-7417] Add a large plan benchmark for HepPlanner#4796zhuwenzhuang wants to merge 1 commit intoapache:mainfrom
Conversation
zhuwenzhuang
force-pushed
the
union_tree_benchmark
branch
2 times, most recently
from
cf1b43e to
c912959
Compare
There was a problem hiding this comment.
What is the purpose of this statement?
There was a problem hiding this comment.
Can you expand this description a bit? What kind of plan is generated, what optimizations are tested, and what this benchmark is really measuring.
There was a problem hiding this comment.
This part is mainly used to evaluate HepPlanner’s ability to optimize large queries. Its performance will be improved step by step with optimizations such as TypeDigest, the firedRuleCache, iterator improvements, GC related optimization, etc. At the moment this benchmark is expected to be pretty slow because the main optimizations have not been committed yet; in the future we can use it as a baseline for incremental optimization.
mihaibudiu
added
LGTM-will-merge-soon
zhuwenzhuang
force-pushed
the
union_tree_benchmark
branch
from
5ea0f94 to
149fea4
Compare
|
2 participants
Add a large plan benchmark for HepPlanner.
We can use it to identify performance bottlenecks.