CircleCI Performance Plan
On This Page
This document describes the Performance plan available to developers.
The Performance plan offers a set amount of credits across a variety of resource classes, per month, which you can customize depending on your build configuration and execution environment.
In addition to a higher amount of network usage included, the Performance plan offers several improvements over the Free plan:
Access to IP ranges
Configure IP-based access to restricted environments with IP ranges. Jobs that have this feature feature enabled will have their traffic routed through one of the defined IP address ranges during job execution.
For more information about this features, please refer to the IP ranges page.
Additional resource classes
Access to some of the larger machine sizes on Docker, Linux, Windows, and macOS. The additional resource classes on the compute type/execution environment give you access to higher CPU and memory limits.
For more information about these resources, please refer to the Executors and images page.
Less queuing with more concurrency
A larger amount of jobs that can run concurrently in your workflows, as described below in Concurrency.
Scalable user seat count
Included is a set number of active users. Additional users can be added by using your credits. If you need more credits, they can be purchased to cover additional users on a per month basis. This process allows you to scale your credit package to align with build activity.
Additional self-hosted runners
A significant increase in the amount of self-hosted runners, allowing you to run more jobs on your own infrastructure. See Self-hosted Runners below for more information.
Custom storage retention
The CircleCI web app allows for the customization of the storage retention periods of artifact, workspace, and cache objects. This allows you to determine how to store each of these objects types in a way that best suits your project. Lowering storage retention periods can also reduce your monthly bill.
Additional support options
Additional support through SLAs (limited hours and days), and support package add-ons. The Performance plan also has access to the community forums, support portal, and our global ticket-based system.
In addition to the upgraded features listed above, the Performance plan also has access to the features listed below. Refer to the Pricing page for more detailed information on credit amounts, included resource classes, key features, and support. Refer to the Resource class features page for details on CPU, memory, network and storage, and credit usage for compute type/execution environment. The following features are available across all of CircleCI’s plans.
CircleCI orbs are shareable configuration packages that enable developers to create private, standardized configurations for use across an organization by different teams. You have access to an unlimited number of private orbs that you can use to securely share across teams and groups.
For more information on private orbs, refer to the Orbs Introduction page.
Concurrency is the ability to run multiple jobs in your workflows at the same time. This is a powerful feature that allows you to decrease your build times and shorten feedback cycles.
CircleCI runners allow you to use your own infrastructure for running jobs, providing more granular control of your own environment and flexibility in building and testing on a wide variety of architectures.
For more information about using CircleCI runners, please see the CircleCI Runner Overview page.
Flaky test detection
The average failed workflow wastes approximately 30 minutes. Detecting flaky tests can save you significant amounts of time in your builds and workflows. Advanced insights are available to help you troubleshoot failed and flaky tests.
For more detailed information about flaky tests, refer to the Test Insights page.
Docker layer caching
Reducing the time it takes to build a Docker image is an important consideration for developers who consistently use these images in their workflows. Consider using Docker Layer Caching (DLC) if building Docker images is a regular part of your CI/CD process. DLC saves image layers created within your jobs, rather than impact the actual container used to run your job. Efficiency features have been specifically designed to take advantage of Docker performance so you can build faster.
For more information about Docker Layer Caching, please refer to the Enabling Docker Layer Caching page.
Help make this document better
This guide, as well as the rest of our docs, are open source and available on GitHub. We welcome your contributions.
- Suggest an edit to this page (please read the contributing guide first).
- To report a problem in the documentation, or to submit feedback and comments, please open an issue on GitHub.
- CircleCI is always seeking ways to improve your experience with our platform. If you would like to share feedback, please join our research community.
Our support engineers are available to help with service issues, billing, or account related questions, and can help troubleshoot build configurations. Contact our support engineers by opening a ticket.
You can also visit our support site to find support articles, community forums, and training resources.
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.