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

Share flux allocation #1441

Closed
wants to merge 2 commits into from
Closed

Conversation

adrienbernede
Copy link
Member

Trying to finally share flux allocation on corona and tioga.

@adrienbernede adrienbernede marked this pull request as ready for review February 7, 2023 15:42
Base automatically changed from woptim/fix-draft-detection-develop to develop February 7, 2023 21:45
@adrienbernede adrienbernede changed the title Attempt to share flux allocation [WIP] Attempt to share flux allocation Feb 7, 2023
@adrienbernede adrienbernede changed the title [WIP] Attempt to share flux allocation Share flux allocation Feb 23, 2023
@adrienbernede adrienbernede self-assigned this Feb 23, 2023
@adrienbernede
Copy link
Member Author

@rhornung67 I think doing so is good practice: we allocate resource only once and run all the jobs in it. Basically, I would argue that it improves the throughput by only allocating once.

We do that on ruby (with slurm), but I didn’t know how to do the same with flux (tried but failed) until I used the slurm-like wrappers to figure it out.

Reminder:
Once the ressource is allocated, there are 2 strategies: "overload" the node with parallel builds, or run the builds sequentially. You always preferred running builds one after the other in RAJA, and the same happens here. In order to speed-up the build, we car increase the number on nodes in the top-level allocation.

  • I marked this WIP because I want to get your approval first, then I’ll merge the associated branch in radiuss-shared-ci.

@adrienbernede
Copy link
Member Author

Closed in favor of #1457.

@adrienbernede adrienbernede deleted the woptim/shared-flux-alloc branch April 12, 2023 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant