> Sent: Saturday, November 10, 2018 at 11:27 AM > From: "Ken Moffat via blfs-support" <[email protected]> > To: "BLFS Support List" <[email protected]> > Cc: "Ken Moffat" <[email protected]> > Subject: Re: [blfs-support] WebKitGTK+-2.22.3 resource build use is insane > > On Wed, Nov 07, 2018 at 11:24:39AM -0600, renodr via blfs-support wrote: > > On 2018-11-06 13:51, Christopher Gregory via blfs-support wrote: > > > Hello, > > > > > > I have just built WebKitGTK+-2.22.3 and it was the most unpleasant > > > experience I have ever had with building blfs. The build killed off > > > the process a total of 4 times due to running out of memory. I have a > > > 6 core machine and 8 gig of ram with a swap partition of 6 gigs. > > > > > > > Try using "export NINJAJOBS=1" and recompile WebKit. > > > I thought I would try this on my 4-core machine - unfortunately, I > accidentally booted the old BLFS-8.3 system instead of the later > build, and had installed all the added extra dependencies before I > realised that. > > This is a ryzen3 with 4 cores, and according to top 7.8 GiB of > memory and 6.0 GiB of swap. > > Using 2.22.3 with the book's instructions for 2.22.2, and not > forcing NINJAJOBS because I figured running 4+2 jobs would probably > be ok, even if slightly slower than forcing 4). A DESTDIR install. > > I was using X, firefox with about 34 tabs, falkon with about 5 tabs, > and 6 instances of urxvt. > > These figures from free, and from du for the directory space, > probably give a fairly accurate indication of the space used. > > Max real mem noted 7214692 > Initial real mem 1363476 (includes the extracted tarball) > change 5851219 > max swap 1339648 > approx total mem 7190857 plus the build space > added directory space 616852 > total 7807709 (7624MiB) > > wkit space starts at 181884 (178MiB) > after install 658408 (643MiB) > change 476524 > and the install 140328 (128MiB) > directory space at end 616852 (602MiB) > > Summary - with (only) 4 jobs, 8GB RAM might be enough if nothing > else is running. > > I'm _surprised_ that Christopher's machine OOM'd with a total of > 14GB RAM+swap and "only" 6 cores (that implies 8 jobs by default in > ninja) - I guess that hyperthreading, if available, was turned off > so that 'top' only shows 8 CPUs. > > ĸen > -- > Is it about a bicycle ? > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page >
Hello Ken, I tried the build without ninja, the way that I have built webkit in the past on this machine, with make -j12 and it ran out of memory as well. I ran make -j9 and there were no more out of memory errors, and it built in around 2 hours 20 mins, whereas with ninja it was 7 hours. I am not sure if hyperthreading is on or off. For me personally, I see absolutely no reason to use ninja for as long as they provide cmake as the build. It is faster for me and less hassle to just drop ninja. I had a look at the ddr3 ram prices, and have noticed that here they are on the climb at $124 for 8 gig. I am still curious to know if swap even gets used on a solid state drive. I guess I will have to get some more ram before ddr3 goes out of stock due to being obsolete. I am not able to afford the ryzen upgrade kits as they are around $1700NZD. Regards, Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
