For caching steps that are taking a long time, consider breaking up the cache into multiple caches. If the job is on the docker executor, consider enabling RAM disk to speed up I/O operations.
Ensure data being added to a workspace is being used downstream and is accessible.
For workspace steps that are taking a long time, analyze the data for anything unnecessary. If the job is on the docker executor, consider enabling RAM disk to speed up I/O operations.
Review how artifacts are used by the team that works in the project and see if adding or removing them would be helpful.
In most cases if artifacts are uploaded to cloud storage, like an s3 bucket, they do not also need to be stored in CircleCI.
Most organizations can benefit from reducing the default storage retention periods without seeing impact, which can save some credits. The common recommendation is below but should be adjusted based on use case and user feedback.
|Artifacts||30 days||7 days|
|Workspaces||15 days||3 days|
|Caches||15 days||7 days|
Next Step: Outside the Config: Project Settings
Previous Step: Outside the Config: Secrets Management
📑 Table of Contents
- Configuration Review Preparation
- Review Each Job for Improvement Opportunities
- Review Each Workflow for Improvement Opportunities
- High Level Improvement Opportunities
- Finalize Review