Caching
WarpBuild provides a blazing fast, unlimited cache for GitHub Action runners. This cache can be used to store build artifacts, dependencies, and other files that are needed across builds. The cache is designed to be fast, reliable, and secure.
Limitations
- WarpBuild Caching is not supported for windows based runners WarpBuild runners.
Performance
Cache save and restore operations are optimized for throughput. Here are some performance benchmarks:
| Concurrency | Operation | Size | WarpCache | GitHub |
|---|---|---|---|---|
| 1 job | Cache save | 500MB | 3s | 11s |
| 1 job | Cache restore | 500MB | 3s | 4s |
| 10 jobs | Cache save | 500MB | 3s | 11s |
| 10 jobs | Cache restore | 500MB | 3s | 4s |
| 25 jobs | Cache restore | 500MB | 3s | 7s |
| 50 jobs | Cache restore | 500MB | 2s | 4s |
| 100 jobs | Cache restore | 500MB | 2.5s | 4s |
| 1 job | Cache save | 5GB | 30s | 131s |
| 1 job | Cache restore | 5GB | 29s | 40s |
| 10 jobs | Cache restore | 5GB | 21s | 35.5s |
| 25 jobs | Cache restore | 5GB | 22s | 34s |
| 50 jobs | Cache restore | 5GB | 23s | 34s |
| 100 jobs | Cache restore | 5GB | 25s | 33s |
The elapsed time and throughput are the median values across 9 runs. The performance is ~35% improvement in cache restores and a ~75% improvement in cache save times.
Expiry
Cache is set to expire after 7 days of last use. It can be manually deleted at any time from the action or using the console.
Pricing
| Metric | Hosted | BYOC |
|---|---|---|
| Storage | $0.20 per GB-month | Free |
| Cache write/restore/list | $0.0001 per operation | Free |
Notes
- WarpBuild cache is compatible with the
actions/cache@v4action.