Review Each Job for Improvement Opportunities: Execution Environment Opportunities

1) Resource Allocation

Optimizing the resource classes of your jobs is an easy way to ensure credits aren’t being wasted. Each job has a resource tab in the UI showing the resource usage throughout the job, which is useful while reviewing jobs individually. CircleCI’s Insights UI offers a view of historical usage for every job in a workflow which is more helpful when doing a config review.

A good rule of thumb is a job should be using 50% - 75% of its resources. If a job is outside of that band try out one of the other resource classes for the execution environment being used.

2) Runner

Runners are useful when a job needs to access data from an internal source or has many dependencies that need to be set up. Those types of jobs can be hard to manage on a CircleCI cloud execution environment and may not be secure. Runner allows you to customize the environment your job is running in and run the job on your own infrastructure which helps support these jobs. Runners do need to be maintained so be sure to take that into account when considering implementing them.

Next Step: Review Each Job for Improvement Opportunities: Opportunities for Jobs with High Duration

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.