On 11/28/2013, 1:21 PM, Mike Hoye wrote:
On 11/28/2013, 12:14 PM, Ehsan Akhgari wrote:
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.
Particularly when that's not an option at all for many current and
prospective contributors, yeah.
Exactly.
Right now the build page on MDN says " More than 2 GB of RAM for recent
Firefox builds, 4 GB or higher recommended", but it's important for our
community to have a more granular understanding of our requirements
there, and to make sure it stays possible - not "efficient" or
"pleasant" or anything, just "possible at all" - to build Firefox on
low-end machines.
Right. FWIW, this is probably as good a forum as any to voice my
objection on the recent trend of recommending people to buy new hardware
to get faster builds. There is a *lot* that we can still do in order to
improve our build times, and while those of us who work for MoCo/MoFo
may be able to enjoy the luxury of asking their employer for a new
machine, we should never assume that for everybody. Back when I was a
non-paid contributor, I used a relatively slow machine for all of my
Mozilla development, and I couldn't really afford the latest and
greatest hardware. If our standard answer to this kind of complaint is
"buy better hardware" then we're excluding a very important part of our
community from consideration. We should not do that.
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
