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

[BBPBGLIB-1069] Added nodes suggestions and more improvements #64

Merged
merged 4 commits into from
Oct 30, 2023

Conversation

st4rl3ss
Copy link
Contributor

@st4rl3ss st4rl3ss commented Oct 18, 2023

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

  • PR description is complete
  • Coding style (imports, function length, New functions, classes or files) are good
  • Unit/Scientific test added
  • Updated Readme, in-code, developer documentation

@bbpbuildbot

This comment has been minimized.

Copy link
Collaborator

@ferdonline ferdonline left a 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

neurodamus/utils/memory.py Outdated Show resolved Hide resolved
neurodamus/utils/memory.py Outdated Show resolved Hide resolved
neurodamus/utils/memory.py Show resolved Hide resolved
@st4rl3ss st4rl3ss force-pushed the dryrun_improvements branch from f403d2b to fafda73 Compare October 20, 2023 15:23
@bbpbuildbot

This comment has been minimized.

ferdonline
ferdonline previously approved these changes Oct 24, 2023
neurodamus/utils/memory.py Show resolved Hide resolved
@st4rl3ss st4rl3ss changed the title WIP - [BBPBGLIB-1069] Added nodes suggestions and more improvements [BBPBGLIB-1069] Added nodes suggestions and more improvements Oct 24, 2023
@bbpbuildbot

This comment has been minimized.

@st4rl3ss st4rl3ss force-pushed the dryrun_improvements branch from 9b39bd9 to 006b91c Compare October 27, 2023 13:31
@bbpbuildbot
Copy link

Logfiles from GitLab pipeline #165331 (:white_check_mark:) have been uploaded here!

Status and direct links:

@st4rl3ss st4rl3ss requested a review from ferdonline October 27, 2023 14:04
@st4rl3ss st4rl3ss merged commit da68e6c into main Oct 30, 2023
2 checks passed
@st4rl3ss st4rl3ss deleted the dryrun_improvements branch October 30, 2023 09:30
WeinaJi pushed a commit that referenced this pull request Oct 14, 2024
## 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
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

Successfully merging this pull request may close these issues.

3 participants