-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Clickbench q32 not working in 32GB RAM #5969
Comments
Looking into this |
I am wondering whether a real TopK operator could reduce the memory usage for q32 to run |
It takes some CPU time on |
confirm it works in
from |
I thought update: ah, looks like |
Before investigating deeper reducing memory usage, we may improve (ps: It already uses the number of CPU cores for parallel reading/sorting, but not memory) But unfortunately, my local run shows it is using peak 34GB in Activity Monitor (macOS) and sometimes pass, sometimes returns the following error Beforeunlimited, Query took 115.120 seconds Afterlimit 16*10^9 bytes (~15GB), 100% fraction
I tried hardcode q32 still got killed |
when running with So I add debug log in https://github.com/apache/arrow-datafusion/compare/main...jychen7:arrow-datafusion:debug-clickbench-q32?expand=1. update: probably the log does not reflect true timing, due to the
|
reg to flamegraph the |
that makes sense. From my debugging above, I think |
with optimized 2.4 GHz 8-Core Intel Core i9 |
Filed #6064 |
I wonder if this query still fails with OOM after the recent improvements. Also, do you guys think #6657 help with this query? |
I do think so |
After #6904 is merged, I have been able to run all click bench queries successfully with 32GB of ram where in datafusion 27.0.0 q32 caused an OOM for me. This I think this is done |
Describe the bug
q32 does not work in
c6a.4xlarge (32GB ram)
, it got killed.To Reproduce
https://github.com/ClickHouse/ClickBench/tree/main/datafusion
Expected behavior
q32 should work
ps: DuckDB takes 5.28s in same type of instance
Additional context
I haven't try in larger instance, e.g.c6a.8xlarge (64GB ram)
or upit works in larger instance, refer to #5969 (comment)
Exec Plan
The text was updated successfully, but these errors were encountered: