From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: /var/tmp on tmpfs
Date: Thu, 8 Feb 2018 19:31:13 -0600 [thread overview]
Message-ID: <ecfd3235-69d0-fb2d-72d2-195ad24e1440@gmail.com> (raw)
In-Reply-To: <p5i8vv$hut$1@blaine.gmane.org>
Nikos Chantziaras wrote:
> On 08/02/18 21:17, Dale wrote:
>> I have 16GBs of memory here and have /var/tmp/portage/ on tmpfs, no
>> ccache. With the growing size of packages, I've had to put several on
>> regular spinning rust to make sure enough space is available. This is
>> my list, so far.
>>
>> www-client/firefox
>> www-client/seamonkey
>> app-office/libreoffice
>> sys-devel/gcc
>> dev-qt/qtwebengine
>> dev-qt/qtwebkit
>
> I'm on 16GB as well, with a 9GB /var/tmp/portage tmpfs, and all of the
> above build fine. No need to build them on disk.
>
> Note that tmpfs does not consume any memory if there's no files in it!
> So you can make your tmpfs larger. Here, 9GB is enough to build the
> above. However, that's of course for when not using --jobs for
> emering. Just regular -jN in MAKEOPTS.
>
>
> .
>
What I run into a lot, Seamonkey and Firefox has a update at the same
time. Since they are both fairly large, they end up compiling at the
same time which makes me run short and it fails when it runs out of
space. So, I just do them on disk and don't worry about it. That said,
those packages would likely benefit from being done on tmpfs.
As it is right now, I usually have Seamonkey, multiple profiles of
Firefox running and other programs as well. Those can easily consume
half of my memory. While tmpfs doesn't "use" anything when it is not in
use, the other stuff does crowd tmpfs.
I'm hoping to upgrade to 32GBs of ram at some point. I could use it for
sure.
Dale
:-) :-)
next prev parent reply other threads:[~2018-02-09 1:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 17:11 [gentoo-user] /var/tmp on tmpfs gevisz
2018-02-08 17:47 ` [gentoo-user] " Nikos Chantziaras
2018-02-08 18:13 ` Rich Freeman
2018-02-08 19:05 ` Nikos Chantziaras
2018-02-08 19:42 ` Rich Freeman
2018-02-08 21:52 ` gevisz
2018-02-08 21:57 ` Rich Freeman
2018-02-08 22:16 ` gevisz
2018-02-09 1:50 ` Dale
2018-02-09 11:52 ` gevisz
2018-02-08 22:32 ` Nikos Chantziaras
2018-02-08 21:31 ` gevisz
2018-02-08 22:19 ` Nikos Chantziaras
2018-02-08 22:32 ` gevisz
2018-02-08 22:38 ` Rich Freeman
2018-02-08 22:50 ` Tsukasa Mcp_Reznor
2018-02-09 10:07 ` gevisz
2018-02-09 11:00 ` Neil Bothwick
2018-02-08 23:42 ` Grant Taylor
2018-02-10 18:56 ` Kai Krakow
2018-02-10 19:38 ` Wols Lists
2018-02-10 19:52 ` Kai Krakow
2018-02-10 20:06 ` Rich Freeman
2018-02-10 21:13 ` Kai Krakow
2018-02-10 21:20 ` Wol's lists
2018-02-10 22:17 ` Kai Krakow
2018-02-08 19:17 ` [gentoo-user] " Dale
2018-02-08 19:41 ` [gentoo-user] " Nikos Chantziaras
2018-02-09 1:31 ` Dale [this message]
2018-02-08 19:50 ` [gentoo-user] " Rich Freeman
2018-02-09 1:24 ` Dale
2018-02-09 10:55 ` gevisz
2018-02-10 19:01 ` [gentoo-user] " Kai Krakow
2018-02-08 21:57 ` [gentoo-user] " gevisz
2018-02-09 1:35 ` Dale
2018-02-08 20:56 ` Grant Taylor
2018-02-08 23:18 ` Wol's lists
2018-02-08 23:28 ` Grant Taylor
2018-02-09 0:02 ` Rich Freeman
2018-02-09 1:15 ` Wol's lists
2018-02-09 2:15 ` [gentoo-user] " Ian Zimmerman
2018-02-09 11:57 ` gevisz
2018-02-10 19:11 ` Kai Krakow
2018-02-09 8:11 ` [gentoo-user] " Neil Bothwick
2018-02-09 10:12 ` Peter Humphrey
2018-02-09 10:58 ` Neil Bothwick
2018-02-10 19:06 ` [gentoo-user] " Kai Krakow
2018-02-09 10:30 ` [gentoo-user] " gevisz
2018-02-09 10:57 ` Neil Bothwick
2018-02-09 10:58 ` Gerrit Kühn
2018-02-09 22:03 ` Grant Taylor
2018-02-10 19:08 ` [gentoo-user] " Kai Krakow
2018-02-10 18:02 ` Kai Krakow
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=ecfd3235-69d0-fb2d-72d2-195ad24e1440@gmail.com \
--to=rdalek1967@gmail.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