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
Cache fallback can be useful in some cases, but in our case it is hindering the CI performance as the cache is growing everyday which results in slower CI times because of the restoring and saving phases.
A fresh cache size is about 450Mb, while currently with fallbacking enabled it has grown to 3.8Gb
Below are some timings taken were we see that having cache fallbacking is doesn't help CI times:
| Caching | Cache Size | Restore Cache | Yarn Install | Save Cache | Total Time Elapsed |
|---------------------------|------------|---------------|--------------|------------|--------------------|
| Cache w/ Fallback (Miss) | 3.81Gb | 2m 50s | 30s | 7m 20s | 10m 40s |
| Cache w/ Fallback (Hit) | 3.81Gb | 2m 50s | 20s | 0 | 3m 10s |
| Cache wo/ Fallback (Miss) | 0 | 0 | 40s | 30s | 1m 10s |
| Cache wo/ Fallback (Hit) | 458mb | 20s | 20s | 0 | 40s |
0 commit comments