CloudBees Core on traditional platforms reference architecture

Estimating your requirements for CloudBees Core on traditional platforms

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

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

    • No. of (Client Master) items = no. of developers * 3.333

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

    • No. of Client Masters 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 Masters (step 2 above) can help you plan how many Client Masters you should install for your initial CloudBees Core on traditional platforms installation. If your estimate is two or more Client Masters, then consider installing a Operations Center to manage these Client Masters.


1. An executor is a slot of execution of build work defined by a Pipeline project/job, typically performed on an agent.
Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.