[Buildbot-devel] database-backed status/scheduler-state project

[Ben Hearsum]

On 3-Sep-09, at 6:07 AM, Axel Hecht wrote:
>
> A big load issue right now are the changesources, but I got those  
> covered.
> If there are more master load issues, why not spin more? Riiiight,  
> let's
> detail on that.
>
> We're not having any load issues on the slaves. We may have not enough
> slaves, and disks, but in general, each slave is fine. That's  
> because we're
> using generic slaves per platform that can do basically any build on  
> that
> platform, independent of branch. We're setting the builds limit to 1  
> per
> slave, and our slaves build what needs to be built.
>
> Adding masters breaks that.

I don't think it does. In the plan Brian describes every master would  
be identically configured - able to handle any job from any branch. It  
allows us to end up with a bunch of masters in different places with  
smaller slave pools. (Does this belong on a Mozilla list rather than  
Buildbot?)