what is the max no of slaves you have added to jenkins master?

[Ankita Nema]

Hi ! 

Want to understand how many slaves can we added to jenkins without breaking it?

-Ankita

[Mark Waite]

Refer to https://jenkins.io/doc/book/architecting-for-scale/ and to https://www.cloudbees.com/blog/scaling-jenkins-slaves and to https://jenkins.io/blog/2016/08/31/scaling-jenkins-at-jenkins-world/ .

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e28efd73-f3c1-45df-b794-0d68f3942220%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen Connolly]

If the hardware for the master is good enough and you are willing to spend time tuning GC parameters... and your builds are not to chatty you should be able to have 1k agents attached... with effort you can get to 2k agents.

I recommend 1-200 agents per master as a practical maximum.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH4X_pDcvzvN-7RmZZqmOG1m%2B%3D020s%2B-JRMywQuj%2B5DLg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Sent from my phone

[Alejandro del Castillo]

On 03/22/2017 07:05 PM, Stephen Connolly wrote:
> If the hardware for the master is good enough and you are willing to
> spend time tuning GC parameters... and your builds are not to chatty you
> should be able to have 1k agents attached... with effort you can get to
> 2k agents.
>
> I recommend 1-200 agents per master as a practical maximum.

In our setup, there are times were we need > 2K agents for testing.
Currently, we do not use Jenkins for testing. Instead, Jenkins calls
into our homegrown Distributed Testing framework, which ends up managing
those 2K nodes. Jenkins is (will be) used for the build, which has ~100
nodes.

In the future, I would like to explore the option to replace our
homegrown framework with Jenkins. But that would push the practical
limit suggested here (<200 agents per master). An splitting those 2K
agents into different masters sounds like over-complicating the
architecture.

Is it a common pattern to offload testing to other frameworks when the
number of test agents cross the threshold suggested here?

--
Cheers,

Alejandro

[Stephen Connolly]

1-200 is the range you can get to without having to *heavily* tune GC or change some Jenkins hidden properties.

2k is the number we have seen a couple of customers get to

I suspect 4k is do-able with some constraints (i.e. all JNLP agents using JNLP4-plaintext (yes plaintext if you want that many agents... TLS will suck too much CPU) and you need lots of cores and memory on your master)

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/14344996-fde1-9395-4cd1-80d7bb6b9fdf%40ni.com.

[Ankita Nema]

Thank you everyone for the response.

This talk was helpful as well.

https://www.cloudbees.com/scaling-jenkins-docker-swarm-kubernetes-or-mesos