On 3 September 2014 14:46, AVIV YAM SIMHAY <[email protected]> wrote:

> How many Remote Nodes can Jenkins manage??
>

With tuning, we have customers who have got to the 500-1000 slave count.


> Are there any limitations/memory issues?
>

No hard limits, you will hit CPU limits and entropy source starvation if
using SSH slaves


>
> What is more effective:
>
> 1) 100 Nodes 1 executes per node ?
> 2) 5 Nodes with 20 executes per node ?
>

Normally the issue is the number of Nodes, so if your nodes can handle the
work of 20 concurrent builds, the 5 remoting channels will be less pain
than 100.

I have done some scaling experiments.

on a AWS M3.large using mostly default JVM sizings

I can get one of:

* 60 JNLP slaves with 2 executors per node. I was able to get up to 60
concurrent builds of the "mock-load" plugin's type before the jenkins
master system load goes above 5 and thus critically impacts the UI
performance on an M3.large

* 60 standard SSH slaves 2 executors per node. I was able to get up to
10-15 concurrent builds of the "mock-load" plugin's type before the jenkins
master system load goes above 5 and thus critically impacts the UI
performance on an M3.large

* 60 of CloudBees Jenkins Enterprise NIO SSH Slaves, 2 executors per node.
I was able to get up to 120 concurrent builds of the "mock-load" plugin's
type. The jenkins master system load never went above 3. There was
back-pressure on the remoting channels once there was more than 25
concurrent builds. The back pressure resulted in increased build times,
however the UI remained performant throughout.


>
> TX!
>
> --
> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to