-
Notifications
You must be signed in to change notification settings - Fork 16
Ashishonce/multiplerunmultiprocessing #17
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
base: master
Are you sure you want to change the base?
Conversation
awmatheson
left a comment
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.
LGTM, we will need to build in some tests for these eventually.
|
added Unit Test basic one, if this format looks fine we will go ahead with that |
|
@ashishonce this looks good, but we are going to wait to merge until we finish the integration tests across all the actions. This should be finished this week. |
|
@awmatheson that makes sense, but just a point. This PR is a breaking change as it changes the run.json format which is a list now. So your integrations tests will still need to update then. |
marvinbuss
left a comment
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.
Before merging this:
- Add integration tests
- Describe features in Readme
This PR is for supporting multiple run submissions as part of a single WF execution.
we are using multiprocessing library to process each entry here. to save the time on parallel waits for execution to complete.
currently creating a pool of processes as 8, but once we agree on this approach we can find an optimal value of processes to start.