You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After talking to a few people about it, it seems that Github Actions Windows runners simply have very slow networking, so this is not something that can be easily fixed in this action.
It might be possible to improve slightly by increasing the compression ratio on Windows, for example.
Writing the cache on Windows is just painfully slow compared to macOS and Linux action runners.
You would think that since GH is owned by Microsoft that they'd optimize the Windows runners a bit more.
Just wanted to add that any improvement on its performance would be much appreciated!
In my workflows though, it takes a very long time to compress the cache with a Zstd compression level of 10, and the network copy time is negligible by comparison.
The post-run phase of
rust-cache
takes a long time on our CI in https://github.com/rustsec/rustsec, but only on Windows.Here's a sample log that shows MacOS cache completing in 38 seconds: https://github.com/rustsec/rustsec/actions/runs/6002426049/job/16278755180?pr=969
And here's the same job on Windows-MSVC, with the post-run phase taking over 5 minutes: https://github.com/rustsec/rustsec/actions/runs/6002426049/job/16278755358?pr=969
This is something that we have consistently observed, not a one-off.
The job definition can be found here: https://github.com/rustsec/rustsec/blob/b6def7c9fa30d7da2b2f569a9cded0f041d68068/.github/workflows/cargo-audit.yml#L36-L54
The text was updated successfully, but these errors were encountered: