CircleCI Resource Class: Optimizing CPU Allocation for Docker‑in‑Docker Workflows

Goal

Reduce build times for Docker‑in‑Docker workflows by selecting the most appropriate resource_class while staying within plan limits and cost constraints.

Constraints & Uncertainty

The resource_class key applies per job, but the actual CPU throughput differs between executor types (Linux, Windows, macOS). Moreover, higher classes (e.g., large, xlarge) consume more credits and may trigger OOM kills if the container exceeds its memory cap. It is unclear how these factors interact when multiple Docker‑in‑Docker jobs run concurrently.

Specific Questions

1. What is the measurable CPU performance difference between large and xlarge classes for Docker‑in‑Docker jobs?
2. How can we detect when a job is hitting CPU limits without an OOM event?
3. Is there a recommended monitoring approach to correlate resource_class selection with build duration and credit usage?