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

Accurately estimate the memory available on the executor #73

Open
calebwin opened this issue Oct 29, 2021 · 1 comment
Open

Accurately estimate the memory available on the executor #73

calebwin opened this issue Oct 29, 2021 · 1 comment
Assignees
Labels
banyan-jl Concerning Banyan.jl enhancement New feature or request

Comments

@calebwin
Copy link
Contributor

calebwin commented Oct 29, 2021

Right now we have a fixed maximum memory usage per worker based on the instance type - and because this isn't accurate we end up assuming that only 30% of it is available which leads to worse performance than needed. Instead, we should have each job that is created, compute the minimum free_memory = begin GC.gc(true); Sys.free_memory end across all workers using min_free_memory = MPI.Reduce(min, free_memory, 0, MPI.COMM_WORLD) and on the head node (where the MPI.Comm_rank(MPI.COMM_WORLD) == 0) we should send this to the client and then send this max_worker_memory to each call to evaluate which stores it in JobInfo.

@calebwin calebwin added enhancement New feature or request banyan-jl Concerning Banyan.jl labels Oct 29, 2021
@cailinw
Copy link
Contributor

cailinw commented Nov 15, 2021

We should ensure that this is not an issue
https://discourse.julialang.org/t/how-to-get-current-julia-process-memory-usage/41734

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
banyan-jl Concerning Banyan.jl enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants