[Buildbot-devel] Recommendations...

Dan Kegel dank at kegel.com
Tue Sep 20 23:40:55 UTC 2011

On Tue, Sep 20, 2011 at 2:59 PM, BRM <bm_witness at yahoo.com> wrote:
> In testing the builds, I've overloaded the system a little - one build
> failed as the build did not communicate in 1200 seconds, probably b/c I had
> 12 builds running at the same time under a single slave.
> So, what is the normal approach for divvying up builds? Do you recommend one
> build-slave per processor/core? Or does it not matter so much?
> How many builds per build slave is normal or do you expect for normal?

I've only been running buildbot for a month; I now have four slaves
running four different kinds of builds, triggered whenever somebody
posts a patch for review, and also when the maintainer does his daily
massive burst of checkins.
My builds take long enough that I only do one build at a time on any slave.

(OT tips: Using ccache was a big, big win.
Presumably Incredibuild or clcache would do the same for visual studio.
Other wins were: using ext4 instead of ext3, using an autoconf cache,
and, especially for amd processors, using cpufreq-set -g performance.)
- Dan

More information about the devel mailing list