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 -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/14344996-fde1-9395-4cd1-80d7bb6b9fdf%40ni.com. For more options, visit https://groups.google.com/d/optout.
