Turn on Work Queue coprocess mode #2779
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should probably be the preferred way of using the work queue executor, as it can speed things up incredibly on shared filesystem supercomputers, and even on my laptop can reduce WQ pytest run time from around 550s to 350s.
khk-globus
approved these changes
Jun 28, 2023
|
this hung in CI trying to run WQ tests... further investigation needed so converting to draft |
|
in CI runinfo logs: 003$ cat ./submit_scripts/parsl.WorkQueueExecutor.block-0.1688148747.9381468.sh.err so this looks like a packaging/install issue of some kind |
…by setup.py entrypoints...
… can use --shuffle!
|
subsequent fiddling has shown there are some subtleties with the PATH mechanism set up by the Makefile... i'll make a separate PR for this first |
|
see PR #2804 for build PATH simplifications which should make coprocesses work |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should probably be the preferred way of using the work queue executor, as it can speed things up incredibly on shared filesystem supercomputers, and even on my laptop can reduce WQ pytest run time from around 550s to 350s.
Type of change
?