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.

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

High memory usage for Finishing stage #364

Open
3 tasks
delucchi-cmu opened this issue Jul 31, 2024 · 0 comments
Open
3 tasks

High memory usage for Finishing stage #364

delucchi-cmu opened this issue Jul 31, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@delucchi-cmu
Copy link
Contributor

Bug report

When importing the large and wide PanStarrs detections table, STSci reports needing 41GiB of memory to complete the Finishing stage.

The Planning, Binning, and Finishing stages currently run inside the controller job, instead of inside dask workers. It can be trickier to add more memory to the controller (for various reasons).

Profile the Finishing stage to look for possible memory hogs and fix them.

Before submitting
Please check the following:

  • I have described the situation in which the bug arose, including what code was executed, information about my environment, and any applicable data others will need to reproduce the problem.
  • I have included available evidence of the unexpected behavior (including error messages, screenshots, and/or plots) as well as a descriprion of what I expected instead.
  • If I have a solution in mind, I have provided an explanation and/or pseudocode and/or task list.
@delucchi-cmu delucchi-cmu added the bug Something isn't working label Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

1 participant