-
Notifications
You must be signed in to change notification settings - Fork 27.8k
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
Save site-packages
as cache in CircleCI job
#24424
Conversation
The documentation is not available anymore as the PR was closed or merged. |
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.
Do we still get updates if there is a release of one of the libraries?
@ydshieh Wait - are the timings of these in the right order? |
@sgugger Yes if we use -U flag. I can do that if you are ok |
Hmm, yes. But could you explain why you have doubts so I can reply in more details? |
|
@ydshieh I just realised my mistake 🙃 I thought it was saying that it takes 2 mins to load with the cache and 30-40s to install by pip. Whereas it's (45 secs + 3-4 mins ) -> (2 mins + 20-30s). My bad! |
The new one should be (45 secs + 2 mins + 20-30s): The first part of cache (in |
Although already been approved - FYI: I just added -U everywhere |
What does this PR do?
Currently, we save
~/.cache/pip
as cache. Takecheck_repository_consistency
job as example:[all, quality]
pip install
takes ~ 3-4 minutesIf we save
.pyenv/versions
as cache too:pip install
takes 20 ~ 30 secondsWe gain 30 ~ 90 seconds (depending on CircleCI's states). Not a big absolute improvement. But for this job which total runtime is ~
5m30s
, we can say > 20% reduction. Ascheck_repository_consistency
andcheck_code_quality
will be run for each PR's each push, probably it's nice to have such reduction.WDYT?