On Fri, Jan 19, 2018 at 12:04 PM, Mick <michaelkintz...@gmail.com> wrote: > > On my old i7 laptop it eats up all 4G of RAM and 4G of swap before it conks > out. So, I dropped the jobs to 3 and --load-average to 2, added a swapfile to > increase disk space and it now builds in around 13 hours. > > I have not used jumbo-build, but perhaps I should?
Well, you can certainly try, but since jumbo-build increases memory use, I suspect you might not be able to get it to complete at all even with -j1. If it did build there is a good chance it would complete faster, even using fewer cores. I'm not sure how exactly jumbo-build combines source files. Hopefully it does it in a way that is consistent each time, so that ccache has some chance of getting hits between builds. That would actually be an advantage to compiling with many smaller units - you might get more cache hits. That is, assuming there aren't header changes in new releases that invalidate large number of cache entries. -- Rich
