Re: r300951 make buildworld duration 18h
It's too bad make(1) can't have a "max parallel jobs" for a particular directory. I believe that some of the llvm build winds up using nearly a gig of RAM per compiled .c file, so when you are running 2 jobs at once, LLVM will swap like mad. If we could add something under the llvm directory "max jobs = RAM/1GB" we could have much faster build worlds. -Alfred On 5/30/16 7:43 AM, Kurt Jaeger wrote: Hi! Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld as # make -j2 buildworld it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom 1.6GHz and 1 GByte RAM and was otherwise unused. Is this the normal buildworld time of today? Yes, this sounds in line with similar setups. I think it spent most of the time in building the llvm... Yes, llvm is a real hog. That's why I normally build on amd64 boxes... ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r300951 make buildworld duration 18h
On Mon, 30 May 2016 07:37:26 -0700 Matthias Apitz wrote > > Hello, > > Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld > as > > # make -j2 buildworld > > it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom > 1.6GHz > and 1 GByte RAM and was otherwise unused. Is this the normal buildworld time > of > today? I think it spent most of the time in building the llvm... > I never build on any of my laptops. I have a 8-thread VM running FreeBSD on a new-ish 6-core Broadwell. It builds world in 35-45 minutes and a new kernel in ~3-5 minutes. I mount it over NFS and install to the laptops when I want to update. Obviously if you only have this Atom based machine then that's not a luxury you have. If that's the case I'd install llvm/clang from ports and skip both clangs from the build. I'd guess it's probably 70+% of the buildworld time on my system and possibly > 80% on yours due to the large C++ memory usage. -M ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r300951 make buildworld duration 18h
Hi! > Yesterday I pulled via svn co ... a fresh r300951 and started the > buildworld as > > # make -j2 buildworld > > it ended today at lunchtime after 18 hours. The laptop has > 2x Intel Atom 1.6GHz and 1 GByte RAM and was otherwise unused. > Is this the normal buildworld time of today? Yes, this sounds in line with similar setups. > I think it spent most of the time in building the llvm... Yes, llvm is a real hog. That's why I normally build on amd64 boxes... -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r300951 make buildworld duration 18h
El lunes, 30 de mayo de 2016 17:11:15 (CEST), Bob Bishop escribió: HI, On 30 May 2016, at 15:37, Matthias Apitz wrote: Hello, Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld as # make -j2 buildworld it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom 1.6GHz and 1 GByte RAM and was otherwise unused. Is this the normal buildworld time of today? I think it spent most of the time in building the llvm… With 1GB it probably spent a lot of its time swapping. the 'make -j2 buildkernel KERNCONF=GENERIC' lasted only 2:40h matthias -- Sent from my Ubuntu tablet http://www.unixarea.de/ ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r300951 make buildworld duration 18h
HI, > On 30 May 2016, at 15:37, Matthias Apitz wrote: > > > Hello, > > Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld > as > > # make -j2 buildworld > > it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom > 1.6GHz > and 1 GByte RAM and was otherwise unused. Is this the normal buildworld time > of > today? I think it spent most of the time in building the llvm… With 1GB it probably spent a lot of its time swapping. > Thx > > matthias > -- > Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ ☎ > +49-176-38902045 > "Die Verkaufsschlager des Buchmarkts geben Auskunft über den Zustand einer > Gesellschaft bzw. > sind, was diese Zeiten angeht, Gradmesser fortschreitenden Schwachsinns. ..." > (jW 19.05.2016) > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Bob Bishop r...@gid.co.uk ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r300951 make buildworld duration 18h
On 05/30/16 10:37, Matthias Apitz wrote: > Yesterday I pulled via svn co ... a fresh r300951 and started the buildworld > as > > # make -j2 buildworld > > it ended today at lunchtime after 18 hours. The laptop has 2x Intel Atom > 1.6GHz > and 1 GByte RAM and was otherwise unused. Is this the normal buildworld time > of > today? I think it spent most of the time in building the llvm... Sadly, this is pretty normal these days :-( It'd be cool if we could drop some of the cross-build targets (like AArch64, AMDGPU, ARM, AVR, Hexagon, MSP430, Mips, NVPTX, PowerPC, Sparc, SystemZ and XCore when on an x86) from machines not in need of them, imb ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
