From: "Morgan Wesström" <gentoo-amd64@pp.dyndns.biz>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Symlinks vs. Bind mounts.
Date: Tue, 12 Aug 2008 09:52:17 +0200 [thread overview]
Message-ID: <48A14131.20904@pp.dyndns.biz> (raw)
In-Reply-To: <pan.2008.08.12.04.45.48@cox.net>
Duncan wrote:
> Now, if you /really/ want to make a difference in portage's speed,
> consider pointing PORTAGE_TMPDIR at a tmpfs. If you've a decent amount
> of memory, it'll make a HUGE difference, since all the files it normally
> creates only temporarily in by default, /var/tmp/portage/* will be
> created in memory (tmpfs) only. Even with a relatively low amount of
> memory, say a gig (we're talking amd64 system context here, after all,
> and a gig has been relatively common since its introduction, not some old
> 1990s 32-bit x86), where tmpfs may be swapped out in some cases, the
> shortest lived files should never hit disk (swap in the case of tmpfs) at
> all. That's a LOT of extreme-latency hard-disk I/O avoided!! If you
> have some serious memory, 2 gig, 4 gig, higher (I have 8 gig), it's even
> MORE effective, as only the biggest merges will ever hit disk at all,
> except of course for the initial PORTDIR/DISTDIR operations and the final
> qmerge to the live filesystem.
This advice caught my attention since I moved my tmp space to Reiserfs
for performance reasons. My knowledge of tmpfs is limited but I think it
is a filesystem that uses RAM and can grow and shrink dynamically,
right? If I follow this advice, what happens when I compile something
like Open Office which allocates 3-4GB in /var/tmp during compilation
and I only have 2GB physical RAM in the computer?
Regards
Morgan
next prev parent reply other threads:[~2008-08-12 7:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 3:28 [gentoo-amd64] Symlinks vs. Bind mounts Juan Fco. Giordana
2008-08-12 4:45 ` [gentoo-amd64] " Duncan
2008-08-12 7:52 ` Morgan Wesström [this message]
2008-08-12 8:18 ` Juan Fco. Giordana
2008-08-12 8:30 ` Beso
2008-08-12 14:38 ` Duncan
2008-08-12 15:05 ` Beso
2008-08-12 15:38 ` Wil Reichert
2008-08-13 1:37 ` Duncan
2008-08-12 15:40 ` Duncan
2008-08-25 10:16 ` Peter Volkov
2008-08-12 19:31 ` Matthias Bethke
2008-08-12 8:23 ` Beso
2008-08-12 9:22 ` Morgan Wesström
2008-08-12 9:29 ` Beso
2008-08-12 10:04 ` Peter Humphrey
2008-08-13 22:54 ` Matthias Bethke
2008-08-14 8:07 ` Duncan
2008-08-14 18:08 ` Richard Freeman
2008-08-14 20:37 ` Matthias Bethke
2008-08-14 22:29 ` Duncan
2008-08-14 20:25 ` Matthias Bethke
2008-08-14 8:07 ` Peter Humphrey
2008-08-15 14:16 ` Adam Mooz
2008-08-12 14:02 ` Duncan
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=48A14131.20904@pp.dyndns.biz \
--to=gentoo-amd64@pp.dyndns.biz \
--cc=gentoo-amd64@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