actions/cache is much slower on Windows
See original GitHub issueHi,
I’m not sure if this is a known issue, or I’m doing something wrong, but this action runs much much slower on windows runners for me. I tried finding issues related to this, but couldn’t find any.
This is not terribly important, but it does force me to wait about four minutes longer for mi CI to run.
You can see this in action here:
- Cache miss: https://github.com/nomiclabs/buidler/runs/722156275
- Cache hit: https://github.com/nomiclabs/buidler/runs/722195141
Note that there are non-windows jobs, where actions/cache
run much faster.
btw, thanks for releasing v2. It’s a HUGE improvement.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:11 (6 by maintainers)
Top Results From Across the Web
extremely slow Network and Disk IO on Windows agent ...
For example, when using the actions/cache@v3 Action to restore something from cache. The cache contains a lot of small files that are then ......
Read more >Improving Performance with Output Caching (C#)
In this article. Enabling Output Caching; Where Content is Cached; Varying the Output Cache; Creating a Cache Profile; Summary. by Microsoft.
Read more >CodeQL analysis for Windows is too slow if I need to compile ...
If your cache exceeds that size limit, you'll always get a cache miss and thus the cache-miss step will always execute. In this...
Read more >Speed Up Your Go Builds With Actions Cache - Mark Phelps
The build was slightly faster than the no cache build, however this small speedup could be attributed to many things beyond our control...
Read more >Slow or poor performance in AutoCAD Products
The response time of AutoCAD is sluggish, showing one or more of the following ... (System Variable) to clear the AutoCAD graphics cache:....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@flybayer We ended up using the Azure Storage SDK for NodeJS instead of Azcopy. This was primarily done so we have better control over versioning and will also work out-of-the-box for self-hosted runners. This change is merged in
toolkit/cache
(see https://github.com/actions/toolkit/pull/497 and https://github.com/actions/toolkit/pull/497) and has been published to NPM. The last step is updating the version used by the cache action (see https://github.com/actions/cache/pull/375) and updating the release tag.actions/cache@v2.1.0
is published. Sorry for the delay getting this out, I found a bug in the version after posting above and had to push out a fix.You can see performance comparison on a 2.5 GB cache file - https://github.com/dhadka/cache-canary/runs/895195362?check_suite_focus=true
Windows is still slightly slower than Ubuntu and Mac at 97 seconds, but this should be a substantial improvement compared to the 4 minutes needed to download the 818 MB cache that started this issue.