[Buildbot-devel] Best way to utilize multiple slaves?

Ben Hearsum bhearsum at mozilla.com
Fri Sep 3 19:37:51 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Use max_builds=1 as an argument to each BuildSlave() rather than a
SlaveLock. You won't have slaves tied up waiting on locks this way, and
only one build at a time will be allowed per slave still!

On 10-09-03 3:01 PM, Ian Zimmerman wrote:
> I have multiple builders and multiple slaves, and I want to maximize
> the number of builds I get through.  Each builder tortures its host
> pretty badly so only one can run at a time on each slave.  I use a
> slave lock on the builder to enforce that.  Right now there's a
> separate Scheduler for each, but I guess there's no reason why I
> couldn't use a single AnyBranchScheduler.
> 
> I configured each builder (say B1 and B2) to use multiple slaves (say
> S1 and S2), and I was naively expecting that when B1 is running on S1
> (taking the S1 instance of the slave lock), and a change for B2 comes
> in, B2 will be scheduled immediately to run on S2.  But that doesn't
> seem to happen; instead B2 is scheduled to run on S1 as well and waits
> for the lock to drop.  The only situation when I get some
> parallelism is when 2 changes for B1 come in at the same time,
> then one of the builds run on S1 and the other on S2.
> 
> So, how can I make this better?  Would using AnyBranchScheduler work?
> Or do I need to refactor to use a single builder for everything?
> 
> Ian
> 
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
> 
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkyBTo4ACgkQJE25Np0n+NvLdwCgkIhWeyfRIrrdGzaepnxvWqlQ
KR0AoKVB4e9Tdw32qhZX6tCuukqriKUB
=U8W3
-----END PGP SIGNATURE-----




More information about the devel mailing list