Repository navigation
Conversation
This allows for optimized implementation given that we know that the input is ordered
|
run benchmarks tpch10 h2o_medium clickbench_partitioned env:
DATAFUSION_RUNTIME_MEMORY_LIMIT: "16G" |
|
run benchmark external_aggr |
|
show benchmarks queue |
|
show benchmark queue |
|
Hi @rluvaton, you asked to view the benchmark queue (#25931 (comment)).
File an issue against this benchmark runner |
|
🤖 Benchmark running (GKE) | trigger CPU Details (lscpu)Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark h2o_medium
env:
DATAFUSION_RUNTIME_MEMORY_LIMIT: "16G"Results will be posted here when complete File an issue against this benchmark runner |
|
🤖 Benchmark running (GKE) | trigger CPU Details (lscpu)Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark clickbench_partitioned
env:
DATAFUSION_RUNTIME_MEMORY_LIMIT: "16G"Results will be posted here when complete File an issue against this benchmark runner |
|
🤖 Benchmark running (GKE) | trigger CPU Details (lscpu)Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark external_aggrResults will be posted here when complete File an issue against this benchmark runner |
|
🤖 Benchmark running (GKE) | trigger CPU Details (lscpu)Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark tpch10
env:
DATAFUSION_RUNTIME_MEMORY_LIMIT: "16G"Results will be posted here when complete File an issue against this benchmark runner |
|
🤖 Benchmark completed (GKE) | trigger Instance: Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark tpch10
env:
DATAFUSION_RUNTIME_MEMORY_LIMIT: "16G"CPU Details (lscpu)Details
Memory Pool PeaksPeak Base:
Pool accounting vs. process RSS Max pool peak is the largest reservation any single query in the run reached; peak RSS covers the whole invocation, including data loading and allocator retention, and the two high-water marks need not coincide in time. The gap is therefore an upper bound on what the pool did not account for, not a measurement of it.
Resource Usagetpch10 — base (merge-base)
tpch10 — branch
File an issue against this benchmark runner |
|
🤖 Benchmark completed (GKE) | trigger Instance: Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark external_aggrCPU Details (lscpu)Details
Memory Pool PeaksPeak Base:
Pool accounting vs. process RSS Max pool peak is the largest reservation any single query in the run reached; peak RSS covers the whole invocation, including data loading and allocator retention, and the two high-water marks need not coincide in time. The gap is therefore an upper bound on what the pool did not account for, not a measurement of it.
Resource Usageexternal_aggr — base (merge-base)
external_aggr — branch
File an issue against this benchmark runner |
|
🤖 Benchmark completed (GKE) | trigger Instance: Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark clickbench_partitioned
env:
DATAFUSION_RUNTIME_MEMORY_LIMIT: "16G"CPU Details (lscpu)Details
Memory Pool PeaksPeak Base:
Pool accounting vs. process RSS Max pool peak is the largest reservation any single query in the run reached; peak RSS covers the whole invocation, including data loading and allocator retention, and the two high-water marks need not coincide in time. The gap is therefore an upper bound on what the pool did not account for, not a measurement of it.
Resource Usageclickbench_partitioned — base (merge-base)
clickbench_partitioned — branch
File an issue against this benchmark runner |
|
🤖 Benchmark completed (GKE) | trigger Instance: Comparing add-fully-ordered-groups-values (8dec018) to 6924c6a (merge-base) diff Run configurationrun benchmark h2o_medium
env:
DATAFUSION_RUNTIME_MEMORY_LIMIT: "16G"CPU Details (lscpu)Details
Memory Pool PeaksPeak Base:
Pool accounting vs. process RSS Max pool peak is the largest reservation any single query in the run reached; peak RSS covers the whole invocation, including data loading and allocator retention, and the two high-water marks need not coincide in time. The gap is therefore an upper bound on what the pool did not account for, not a measurement of it.
Resource Usageh2o_medium — base (merge-base)
h2o_medium — branch
File an issue against this benchmark runner |
Which issue does this PR close?
None
Rationale for this change
Improving performance. there is no need to do unnecessary computation when the group by columns are fully sorted
What changes are included in this PR?
Implemented
GroupValuesfor new structFullyOrderedGroupValuesthat avoid keeping hash map and map probingWhat is the testing strategy for this PR?
existing tests
Are there any user-facing changes?
no