[Buildbot-devel] Playing nice on loaded buildslaves - sharing buildmasters between projects?

tom fogal tfogal at sci.utah.edu
Fri Oct 19 09:43:58 UTC 2012

I should have mentioned another option: disable Linux's overcommit 
policy.  Then you won't even be able to start a VM if you don't have the 
memory, so it'll fail up front instead of (inevitably) while you're 

Also in your situation you probably want to enable kernel samepage 
merging, if you haven't already.


On 10/19/2012 09:48 AM, Dan Kegel wrote:
> Perhaps unwisely, I have a whole bunch of buildslaves
> running in lxc containers (very lightweight vm's) on one
> machine, all talking to different buildmasters.
> If I'm not careful, I can run out of memory because too
> many builds happen at once.
> A few ideas for how to prevent this:
> - don't run so many buildslaves on one physical machine
> - use a single buildmaster
> - vary the hour and minute parameters to timed.Nightly() in master.cfg.
> - make the build script use -j1 instead of -n$ncpus when load is high
> - make build script terminate on startup if the load is really high.
> - use distcc and let it handle load balancing
> I'm not sure how I would go about using a single buildmaster
> for all projects, and still have separate waterfalls, one
> for each project.  Is that possible?
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel

More information about the devel mailing list