Re: [PATCH 2/2] build-many-glibcs: Impose a memory limit on build processes.

[Joseph Myers <joseph at codesourcery dot com>]

On Sun, 9 Jul 2017, Zack Weinberg wrote:

> The limit can be configured with the --memory-limit command line switch.
> The default is 1.5 gigabytes or physical RAM divided by the number of
> jobs to run in parallel, whichever is larger.  (Empirically, 1.5 gigs
> per process is enough for everything but the files affected by GCC
> bug 78640, but 1 gig per process is insufficient for some of the math
> tests and also for the "genautomata" step when building compilers for
> powerpc64.)

I think the default should allow more room than just being slightly above 
what's enough right now in a particular build (does --enable-checking, 
i.e. GCC mainline, use more memory? I don't know offhand) - say 3 GB.  
(The default may be different from the threshold for the warning for 
values expected to be too small.)

> +    def set_memory_limits(self):
> +        """Impose a memory-consumption limit on this process, and therefore
> +           all of the subprocesses it creates.  The limit can be set
> +           on the command line; the default is either physical RAM
> +           divided by the number of jobs to be run in parallel, or 1.5
> +           gigabytes, whichever is larger.  (1GB is too small for
> +           genautomata on MIPS and for the compilation of several
> +           large math test cases.)

Is it both powerpc64 and MIPS that need more than 1 GB, then?

-- 
Joseph S. Myers
joseph@codesourcery.com