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

Umpire Memory Pool Usage #1008

Closed
PaulMullowney opened this issue Nov 10, 2023 · 4 comments
Closed

Umpire Memory Pool Usage #1008

PaulMullowney opened this issue Nov 10, 2023 · 4 comments

Comments

@PaulMullowney
Copy link
Contributor

Is there any way to tell how much of an Umpire memory pool is being used at a given point in a Hypre solve?

-Paul

@victorapm
Copy link
Contributor

victorapm commented Nov 10, 2023

Hi Paul, currently not. But that's something that could be implemented in hypre, see umpire's getCurrentSize:

https://github.com/LLNL/Umpire/blob/58be0db4455643893287a102d3f7409846e354b1/src/umpire/Allocator.hpp#L107-L115

I'm not sure though how this would work in the scenario where a GPU is being oversubscribed with multiple MPI ranks (if we want to compute overall memory utilization percentage)...

@PaulMullowney
Copy link
Contributor Author

Thanks Victor. That's a helpful pointer.
-Paul

@victorapm
Copy link
Contributor

This is the C interface for the function I mentioned (hypre uses umpire via its C interface): https://github.com/LLNL/Umpire/blob/58be0db4455643893287a102d3f7409846e354b1/src/umpire/interface/c_fortran/wrapAllocator.cpp#L97-L105C2

If you implement something, please let me know :)

@victorapm
Copy link
Contributor

Paul, this seems to be resolved, so I'm closing. Thanks!

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

No branches or pull requests

2 participants