CloudBees CI on traditional platforms reference architecture

1 minute readReference

Estimating your requirements for CloudBees CI on traditional platforms

You can estimate your organization’s client controller and executor [1] requirements, based on the number of developers in your organization. These requirements should provide a good basis for your initial CloudBees CI on traditional platforms installation.

  1. Estimate the total number of client controller items (i.e. Pipeline projects, jobs and other items configured on a client controller) in your CloudBees CI on traditional platforms installation. This can be based on the approximation:

    • No. of (client controller) items = no. of developers * 3.333

  2. Using this "no. of items" value, estimate the number of client controller instances required for your CloudBees CI on traditional platforms installation. Typically, each CPU core of the hardware on which the client controller is installed can support a maximum of 100 client controller items. If, for example, your client controller’s hardware has 5 CPU cores, then the client controller can support a total of 500 items. Assuming this hardware arrangement for each client controller:

    • No. of client controllers required = no. of items / 500

  3. Last, you can estimate the number of executors based on this simple formula/approximation:

    • No. of executors = no. of items * 0.03

Your estimated required number of client controllers (step 2 above) can help you plan how many client controllers you should install for your initial CloudBees CI on traditional platforms installation. If your estimate is two or more client controllers, then consider installing the operations center to manage these client controllers.


1. An executor is a slot of execution of build work defined by a Pipeline project/job, typically performed on an agent.