-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BBPBGLIB-1069] Added nodes suggestions and more improvements #64
Conversation
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot. My suggestions go simply in the direction where user might run neurodamus is any machine, so we should always print stats for a common BB5 node, plus eventually the current node if different
f403d2b
to
fafda73
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
9b39bd9
to
006b91c
Compare
Logfiles from GitLab pipeline #165331 (:white_check_mark:) have been uploaded here! Status and direct links: |
## Context Introduces nodes suggestions for users. This functionality is one of the main results that should come out of the introducing of the dry run workflow. Nodes suggestion is calculated taking in mind the amount of memory present in the current machine where the code has been run. It also takes into consideration the variable amount of overhead necessary dependent on the amount of ranks used for the execution. ## Scope Most of the changes are independent of the main workflow and only touch the dry-run workflow. A prompt has been added at the end of any dry run workflow to provide a suggestion for user on how many nodes are needed in order to have a reasonable amount of memory available to run the simulation. ## Testing Since the MR just introduces a small text prompt for the user, no tests are necessary. Full dry run workflow tests will be introduced once the workflow gains a certain "maturity". ## Review * [x] PR description is complete * [x] Coding style (imports, function length, New functions, classes or files) are good * [x] Unit/Scientific test added * [x] Updated Readme, in-code, developer documentation
Context
Introduces nodes suggestions for users.
This functionality is one of the main results that should come out of the introducing of the dry run workflow.
Nodes suggestion is calculated taking in mind the amount of memory present in the current machine where the code has been run. It also takes into consideration the variable amount of overhead necessary dependent on the amount of ranks used for the execution.
Scope
Most of the changes are independent of the main workflow and only touch the dry-run workflow. A prompt has been added at the end of any dry run workflow to provide a suggestion for user on how many nodes are needed in order to have a reasonable amount of memory available to run the simulation.
Testing
Since the MR just introduces a small text prompt for the user, no tests are necessary.
Full dry run workflow tests will be introduced once the workflow gains a certain "maturity".
Review