-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql: performance regression on TPC-H Q17 between 20.1 and 20.2 #55787
Comments
Here is what I got when running Q17 on a single node cluster on my laptop.
Based on these observations it seems that #48058 is the cause of the slowdown. In the local environment it increased the latency by 15% or so, and possibly in the distributed environment the increase could explain 20-30% performance degradation we're seeing when comparing against 20.1 version (or it could be some other changes). Interestingly, the dynamic batch size behavior appears to have a very minor positive impact. |
Reducing join reader batch size hint for "ordering" strategy from 2MB to 256KB seems to give us those 15% back. I'll kick off a run of |
5 runs of
(the lower the score, the better). Closing the issue as an unfortunate regression that occurred because of the change that is actually beneficial in most cases. |
I reran all TPCH queries (via
tpchvec/perf
test, 35 times total) with the default configs on 20.1.7 and 20.2.0-rc.2, and we've improved significantly on many of them, but on query 17 there is a regression:Last time we did a similar experiment some time around July, and we also saw a similar regression
The plan for the query hasn't changed this year (based on
tpch_vec
logic test), so my guess is that it might be due to the changes around join reader (#48058, #49669). cc @asubiottoThe text was updated successfully, but these errors were encountered: