On 11/28/2013, 2:29 AM, Gabriele Svelto wrote:
On 28/11/2013 08:09, Gregory Szorc wrote:
Peak RSS likely has increased significantly (hundreds to gigabytes
range).
OK, that's what I was curious about.
Memory is cheap and getting cheaper. Nobody paid by Mozilla to develop
Firefox should have a machine with less than 16 GB. Adding 25%+ to build
times to accommodate people on old hardware is not acceptable.
My desktop machine's got 32GiB but there's a number of contributors or
partners' employees that might not be on such beefy hardware. We often
had issues in the past with potential FxOS contributors running into OOM
errors while doing their first build. Another common case of OOMs are
people building inside a VM. Just yesterday I helped another mozillian
figure out why his FxOS build had started to fail. It turned out he was
building inside a VM with too many jobs and too little memory dedicated
to it.
Please file a bug (and CC me) with more details about where the build
fails, how much memory the machine has, and how much memory each
compiler invocation consumes (test with make -j1). We can adjust the
number of files we build in one chunk per directory, so this is easily
fixable. "Buy more RAM" is a terrible answer to this kind of problem.
Also I'm not sure how our automated build infrastructure copes with this
but I would assume we should have enough memory there (or if we don't
the memory/CPU time trade-off is probably worth the improvement in build
times).
Note that I would expect the peak memory usage in any build to be
diminished by the linker's memory usage. If the compiler invocations
end up consuming an exceeding amount of memory in a given directory, we
should fix that.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
