Job hardware requirements
System requirements for your job hardware vary considerably based on the size of your Continuous Delivery for PE installation, the type of jobs you run, and how frequently you run them.
The size of the load placed on a job hardware server determines how robust that server's resources need to be. Determining that load involves a huge number of variables, from the number of jobs that run concurrently to the languages those jobs are written in. As a result, it's nearly impossible to provide one-size-fits-all system requirements for job hardware.
Instead, we've developed a sizing chart based on the estimated number of concurrent jobs a job hardware server is expected to regularly handle. While this chart represents our best estimates and understanding, it's provided only as a starting point. Testing and experience will help you fine-tune your job hardware and determine the optimum resource configuration for your installation's unique circumstances.
|Estimated concurrent job load||Memory||Disk storage||CPUs|
|2 - 4 concurrent spec tests||4 GB||100 GB||2|
|4 - 8 concurrent spec tests||8 GB||100 GB||4|
|6 - 12 concurrent spec tests||8 GB||100 GB||6|
- Disk storage requirements are minimal, and don't increase with added load. After a job run is complete, the job's log is passed to the object storage, and all data related to the job run is erased from the job hardware.
- You can run more jobs concurrently without increasing CPUs, but the jobs will run more slowly.
Job hardware requirements for Docker-based jobs
To run Docker-based jobs, your job hardware must have a modern
version of Docker CE or Docker EE installed. The
module is our preferred way to install Docker
and keep it up to date.
Job hardware used for Docker-based jobs also requires internet access. If you're working in an air-gapped environment, set up an internal Docker registry by following the Docker documentation.