Comment 3 for bug 746822

On 08/06/11 10:26, Robert Collins wrote:
> On Wed, Jun 8, 2011 at 9:07 PM, Jelmer Vernooij
> <email address hidden> wrote:
>> Some other things that we can do to improve the memory usage:
>>
>> * deploy a newer version of bzr which uses less memory (this is in the pipeline)
> +1
I'll have a look at this - bzr-builder also needs to be updated, might
as well do both.

>> * increase the ulimits for the recipe build jobs on the buildds; if I
> remember correctly they were set pretty low because of responsiveness
> issues with the buildds that should be less of an issue now the buildd-
> manager has moved to twisted
>
> The buildd manager was always twistd. The buildds need to be
> responsive or the manager will consider them dead.
Sorry, I mean until the buildd manager was made properly twisted by
bigjools and jml last year.

I recall there were issues with builders going AWOL when they were
building large recipe builds, and taking a really long time (> 30
seconds or something) to respond to simple "are you alive" query ? The
strict ulimits were put in place specifically to try to mitigate that,
but the issue later disappeared because of another fix, roughly around
the same time the buildd manager was made fully twisted. IMBW.

I don't see any ulimits in place (in the lib/canonical/buildd scripts)
for non-recipe builds; I would expect the limits to be the same for both
regular and recipe builds.

Cheers,

Jelmer