Make github CI workflow faster #225
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
JeanMainguy
changed the title
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 PR implements two adjustments to speed up the GitHub CI process:
It utilizes multiple CPUs instead of just one. The number of available cores is assessed and utilized in ppanggolin commands that support multiprocessing. GitHub runners typically have 4 CPUs available. You can find more information about runner resources in GitHub's documentation.
It limits testing to only the oldest and latest supported Python versions, rather than testing on all versions. While this change may not necessarily reduce the overall workflow duration, it significantly reduces computational load per execution.
These adjustments result in a 2x decrease in duration time, reducing it from approximately 40 minutes to 20 minutes.