Update README to include zstd workaround for windows. by lvpx · Pull Request #912 · actions/cache (original) (raw)
This PR contains the following changes:
- Move
Cache segment restore timeoutsection toKnow practices and workarounds - Add
yamlformatting for actions code blocks - Add zstd workaround for windows and zstd requirement for self-hosted windows runners.
…ve Cache segment restore to Known Practices section.
lvpx changed the title
Pdotl/readme update 1 Update README to include zstd workaround for windows.
Hi @wrexbe, I agree. This workaround is being used by customers vs using gzip which is even slower. We are simply documenting the same. We are looking into improving windows performance for cache by looking at several alternatives.
lvpx and others added 3 commits
…-1' into pdotl/readme-update-1
| ``` |
|---|
| ## Cache segment restore timeout |
| ## Known practices and workarounds |
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to create separate file for this?
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would yes. We can move it to another file.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
lvpx deleted the pdotl/readme-update-1 branch
This was referenced
Sep 30, 2022
This file contains hidden or 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
[ Show hidden characters]({{ revealButtonHref }})