This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 2/2] build-many-glibcs: Impose a memory limit on build processes.
On Mon, 10 Jul 2017, Zack Weinberg wrote:
> So I actually wanted to make it _lower_ -- my usual build machine has
> 8 CPUs and 8G of RAM, so anything higher than 1G/concurrent process
> risks going into swap. But then genautomata. :-(
>
> I think what I'll do -- after the powerpc situation is resolved -- is
> put together some instrumentation to find out how much RAM is used
> both on average and at worst; that will let us make more informed
> decisions about the defaults. I'll try GCC mainline as well.
Since there are six SH multilibs, 6 * limit + (CPUs - 6) * average is
probably the peak amount that gets used in practice. (My bots use a limit
of 16 GB - set before starting build-many-glibcs.py - on systems with 32
hardware threads and 128 GB RAM.)
Also note incidentally: if anyone wanted to use build-many-glibcs.py to
run build tools that had been built with Address Sanitizer, they'd need to
disable the limits (Address Sanitizer uses a very large amount of address
space, I think 16 TB).
--
Joseph S. Myers
joseph@codesourcery.com