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
Describe the enhancement
Hello! I'm working on optimizing some of our CI workloads. One of the things that I noticed in that process is that the actions/cache logic runs download/upload and compress/decompress as separate actions. I think we can squeeze more performance out by utilizing streams and skipping writing to and reading from the fs for the cache.
For the use case I'm looking at specifically, the cache save step takes ~38s and the restore takes 22s (~4s download, ~18s uncompress). I think the biggest benefit for us will come from upload, but I can't tell from the logs how long each portion takes.
Is this something you'd be open to? I am open to help make this happen, but I wanna get confirmation before digging any further.
Code Snippet Before:
awaitdownload(url,location);// <-- downloads, saves to diskawaituntar(location);// <-- reads from disk, doesn't start until download is complete
After:
awaitdownloadAndUntar(url);// <-- streams, avoids writing to then reading from fs, starts decompressing immediately
Additional information
Add any other context about the feature here.
The text was updated successfully, but these errors were encountered:
Describe the enhancement
Hello! I'm working on optimizing some of our CI workloads. One of the things that I noticed in that process is that the actions/cache logic runs download/upload and compress/decompress as separate actions. I think we can squeeze more performance out by utilizing streams and skipping writing to and reading from the fs for the cache.
For the use case I'm looking at specifically, the cache save step takes ~38s and the restore takes 22s (~4s download, ~18s uncompress). I think the biggest benefit for us will come from upload, but I can't tell from the logs how long each portion takes.
Is this something you'd be open to? I am open to help make this happen, but I wanna get confirmation before digging any further.
Code Snippet
Before:
After:
Additional information
Add any other context about the feature here.
The text was updated successfully, but these errors were encountered: