Open justinj opened 5 years ago
We have marked this issue as stale because it has been inactive for 18 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 5 days to keep the issue queue tidy. Thank you for your contribution to CockroachDB!
We have marked this issue as stale because it has been inactive for 18 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to CockroachDB!
TPCH Analyzed suggests a cute optimization which ostensibly helps with Q1:
Turn
into
This issue is for tracking this optimization.
I've done some brief investigation, on my laptop and gceworker I saw no noticeable benefit to Q1 via performing this optimization. I ran a simplified experiment on my laptop, where I benchmarked the performance of these two queries:
"optimized":
"unoptimized":
With 10 interleaved runs of each, the results I got were:
Which is not especially convincing that this optimization is worthwhile for us right now.
In this particular example we were probably heavily limited by our scan speed, rather than our CPU performance, so it might be worth looking into this more, especially if our scan speeds improve in the future.
Jira issue: CRDB-4628