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

Memory limits for local executor #42

Open
jshleap opened this issue Jun 27, 2022 · 3 comments
Open

Memory limits for local executor #42

jshleap opened this issue Jun 27, 2022 · 3 comments

Comments

@jshleap
Copy link

jshleap commented Jun 27, 2022

I have noticed that redun seems to reserve memory even in local executors. Is there a way to tune that? or I am wrong on this assumption?

@mattrasmus
Copy link
Collaborator

Hi @jshleap! Thanks for the question. I don't believe we set memory limits on local executors. Are you getting some behavior that suggests otherwise?

reserve memory even in local executors

Unless by "reserve" you mean preallocating memory. redun isn't doing anything unusual in that regard more than what multiprocessing thread and process pools typically do (FWIW, that is how redun implements the local executors). Let me know if that helps, or if I misunderstood the question.

@jshleap
Copy link
Author

jshleap commented Jun 27, 2022

Thanks for the answer @mattrasmus. I assumed that there is pre-allocation of memory per task as I am running out of memory for a medium sized dataset. I guess I should control the max_workers instead.

@mattrasmus
Copy link
Collaborator

max_workers will work to limit parallelism across all tasks. If its just one task that should have parallelism limits, check out the limits config option: https://insitro.github.io/redun/config.html?highlight=limit#limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants