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

Auto-detect memory limits #37

Open
jhtu opened this issue Apr 21, 2020 · 1 comment
Open

Auto-detect memory limits #37

jhtu opened this issue Apr 21, 2020 · 1 comment

Comments

@jhtu
Copy link
Collaborator

jhtu commented Apr 21, 2020

Automatically detect the max_vecs_per_node. Or in the future, max_vecs_per_communicator. This would require some fancier things, like determining the available RAM and the size of a vector object. It might not be possible since some memory is used by the vector objects when doing inner products, etc. We could leave a safety factor though, and maybe leave space for 1-2 vecs/modes for scratch space for the user's functions.
@jhtu
Copy link
Collaborator Author

jhtu commented Apr 21, 2020

Moved from old todo.txt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jhtu