On Tuesday, 5 December 2017 11:13:53 GMT Raffaele Belardi wrote: > Wols Lists wrote: > >> If a tmpfs fills up, the excess gets swapped out, but with 32GB RAM here > >> I > >> haven't yet seen any swap used at all - not even in an emerge -e world. > > > > Same here. Note that tmpfs defaults to half ram, so that would give you > > a 16GB /var/tmp/portage. With 16GB ram here, that would probably cause > > things like emerging libreoffice or firefox or gcc to abort. > > Not really, libreoffice and gcc compile slowly but fine here with 3Gb RAM > and 3Gb spin-disk swap, and using PORTAGE_NICENESS=19 the system is still > usable (rebuilding world for the profile switch right now). That's with an > LXDE desktop, Gnome3 survived only a few months, _that_ was really > unusable. > > $ free > total used free shared buff/cache > available Mem: 3102960 1316120 964848 370488 > 821992 1123260 Swap: 3076344 91648 2984696 > > $ df > Filesystem Size Used Avail Use% Mounted on > tmpfs 304M 1.9M 302M 1% /run > none 1.5G 0 1.5G 0% /dev/shm > > $ eix -I libreoffice > [I] app-office/libreoffice > Available versions: 5.4.2.2 (~)5.4.3.2 > Installed versions: 5.4.3.2 > > $ gcc-config -l > [1] i686-pc-linux-gnu-7.2.0 * > > $ qlop -gH libreoffice | tail -n 2 > libreoffice: Wed Nov 22 18:13:17 2017: 12 hours, 37 minutes, 9 seconds > libreoffice: 13 times > > $ qlop -gH gcc | tail -n 2 > gcc: Mon Dec 4 21:50:26 2017: 3 hours, 9 minutes, 7 seconds > gcc: 80 times > > $ uname -a > Linux ws2912 4.14.0-gentoo #1 SMP Fri Nov 17 09:31:56 CET 2017 i686 Intel(R) > Pentium(R) 4 CPU 3.40GHz GenuineIntel GNU/Linux
How does gcc-7.2.0 compare with 6.4.0 in terms of memory efficiency? I'm asking because on a 1st gen i7 and 4G of RAM, for the first time ever, www-client/chromium-62.0.3202.94 failed to build because of an internal compiler error. I'm guessing it had something to do with me always running MAKEOPTS="-j5 -l12.8", but I can't recall what formula I used to arrive at this load number ... I'm trying again with emerge --load-average 4 to see if it compiles this time. When I switched to profile 17.0 I noticed a 2.5x increase in time it took to emerge the previous version of chromium, as part of 'emerge -e @world', but I hoped this was a one off mishap because I was using the PC at the time: Thu Nov 9 17:44:58 2017 >>> www-client/chromium-62.0.3202.89 merge time: 8 hours, 12 minutes and 30 seconds. Mon Dec 4 11:39:36 2017 >>> www-client/chromium-62.0.3202.89 merge time: 20 hours, 2 minutes and 4 seconds. With only 4G RAM the poor thing was thrashing the disk swapping on and off forever, becoming completely unresponsive for minutes at a time. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.