Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upCirrus CI: proof of concept #1
Conversation
This comment has been minimized.
This comment has been minimized.
|
I've also tried to run 30 CPUs but the time improvement was pretty low comparing to 8 CPU. |
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.
fkorotkov commentedFeb 4, 2019
•
edited
In the lights of the recent post about Rust looking for alternative CIs, I've made a quick attempt to migrate to Cirrus CI.
Thankfully Rust's CI build is already Dockerized and Cirrus CI supports Dockerfile as an environment for tasks. So there is no need to do the Docker image building and caching like in the current setup. Cirrus CI does it automatically based on Dockerfile content.
As you can see the config is small and pretty simple and Cirrus CI performs quite well since it uses 8 CPU and 24G of memory.
I also tried to run with less CPU and memory and noticed that more resources don't make the build linearly faster. I assume there is a great potential in optimizing the build itself to use all available CPUs.
@pietroalbini PTAL and let me know if you'd like to evaluate something else.