From: Raffaele Belardi <raffaele.belardi@st.com>
To: <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] is multi-core really worth it?
Date: Tue, 5 Dec 2017 12:13:53 +0100 [thread overview]
Message-ID: <8ad51522-2b55-f976-8908-9ad48fe4be52@st.com> (raw)
In-Reply-To: <5A267913.5030902@youngman.org.uk>
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
next prev parent reply other threads:[~2017-12-05 11:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 6:52 [gentoo-user] is multi-core really worth it? Raffaele Belardi
2017-11-22 7:21 ` R0b0t1
2017-11-22 7:26 ` Jeremi Piotrowski
2017-11-22 8:23 ` Neil Bothwick
2017-11-22 8:34 ` David Haller
2017-11-22 10:07 ` [gentoo-user] " Martin Vaeth
2017-11-22 11:26 ` David Haller
2017-11-23 22:47 ` Martin Vaeth
2017-11-22 13:12 ` [gentoo-user] " Raffaele Belardi
2017-11-22 13:23 ` J. Roeleveld
2017-11-22 14:11 ` Tsukasa Mcp_Reznor
2017-11-22 14:34 ` Wols Lists
2017-11-22 16:27 ` J. Roeleveld
2017-12-05 4:11 ` Taiidan
2017-12-05 4:17 ` R0b0t1
2017-12-05 10:09 ` Peter Humphrey
2017-12-05 10:46 ` Wols Lists
2017-12-05 11:13 ` Raffaele Belardi [this message]
2017-12-05 11:39 ` Mick
2017-12-05 13:07 ` Peter Humphrey
2017-12-05 13:57 ` Wols Lists
2017-12-05 14:13 ` Peter Humphrey
2017-12-05 21:56 ` Neil Bothwick
2017-12-06 13:29 ` Wols Lists
2017-12-06 15:34 ` Alan McKinnon
2017-12-06 16:07 ` Wols Lists
2017-12-06 23:51 ` [gentoo-user] " Ian Zimmerman
2017-12-06 16:12 ` [gentoo-user] " Wols Lists
2017-12-06 17:24 ` Kai Peter
2017-11-22 7:48 ` David Haller
2017-11-22 8:32 ` J. Roeleveld
2017-11-22 8:57 ` David Haller
2017-11-22 12:16 ` Peter Humphrey
2017-11-22 16:36 ` Neil Bothwick
2017-11-28 10:07 ` [gentoo-user] " Raffaele Belardi
2017-12-01 10:39 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ad51522-2b55-f976-8908-9ad48fe4be52@st.com \
--to=raffaele.belardi@st.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox