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.

Usage

WarpBuild cache can be used by replacing the actions/cache@v4 action with the warpbuilds/cache action. The warpbuilds/cache action is fully compatible with the actions/cache@v4 action and can be used as a drop-in replacement.

Refer to the GitHub Actions cache documentation for more information on how to use the cache.

uses: WarpBuilds/cache@v1

The cache is designed to be fast, reliable, and secure. The cache is available on all Linux based runners and is enabled by default.

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.

Pricing

Metric	Price
Storage	$0.20 per GB-month
Cache write/restore/list	$0.001 per operation

Notes

1. actions/setup-* will continue to use the GitHub cache. WarpBuild cache support for these setup actions is coming soon.
2. WarpBuild cache is compatible with the actions/cache@v4 action.