Figuring out how Data Usage of the cache and workspaces are charged in CircleCI can be a little confusing. The simple answer is that we charge when data is persisted to the cache or workspace. There is some nuance to how persisting works between caching and workspaces, so this article is here to help explain.
Persisting to the cache only occurs when changes are made to data in the cache. Since this means that we will only charge you when the cache is updated, this can be more cost-effective than using workspaces but can be less reliable, as a cache miss can occur.
Persisting to the workspace will occur on each build execution, which means you will be charged network usage per build. This can help keep your environments more consistent, but may not be as cost-effective as using the cache
- No Cache Found and Skipping Cache Generation
- Creating a "daily" cache
- Can I cache my dependencies on CircleCI?