On 11/28/13, 12:21 PM, Gabriele Svelto wrote:
On 28/11/2013 06:06, Gregory Szorc wrote:
On de5aa094b55f, we're now down to:
Wall 7:37 (457)
User 45:38 (2738)
Sys 3:54 (234)
Total 49:32 (2972)
That's with WebRTC and ICU enabled.
Looking at my own stats while building I was wondering if anybody has
looked at peak memory consumption with unified sources. Since now we're
compiling up to 16 files per compiler instance I would imagine that peak
memory consumption has increased, possibly significantly. This could be
offset by the fact that most of the files will be sharing headers but I
still wonder how much of an impact it has.
Peak RSS likely has increased significantly (hundreds to gigabytes
range). However, you can offset this by building in non-unified mode
(--disable-unified-compilation) or by decreasing the concurrency of
building (make -j).
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. We can,
however, add build system warnings when "inadequate" hardware is
detected. Bug 914431 is related. Long term, we could explore having the
build system adapt to the system's abilities e.g. by dynamically
adjusting concurrency based on detection of swapping. Things like this
are low in priority compared to making builds faster for the majority of
builders. In the interim, patches welcome.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
