Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Substantial memory usage in dask.order #11055

Open
fjetter opened this issue Apr 18, 2024 · 0 comments
Open

Substantial memory usage in dask.order #11055

fjetter opened this issue Apr 18, 2024 · 0 comments
Labels
needs triage Needs a response from a contributor

Comments

@fjetter
Copy link
Member

fjetter commented Apr 18, 2024

I'm currently still working on a reproducer but I've seen dask.order taking up a substantial amount of memory

Particularly, I've seen this set

dask/dask/order.py

Line 672 in 00a5d92

new_set.update(r_child)
grow to several GB of memory

image

This is likely not only slow but can also crash the scheduler
@github-actions github-actions bot added the needs triage Needs a response from a contributor label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs triage Needs a response from a contributor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fjetter