From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: tmpfs help
Date: Wed, 13 Feb 2008 17:22:59 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.02.13.17.22.58@cox.net> (raw)
In-Reply-To: 200802131346.26316.volker.armin.hemmann@tu-clausthal.de
Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de> posted
200802131346.26316.volker.armin.hemmann@tu-clausthal.de, excerpted below,
on Wed, 13 Feb 2008 13:46:26 +0100:
> On Mittwoch, 13. Februar 2008, Duncan wrote:
>>>removed lots of irrelevant 'my hardware is so cool' stuff'.
>
> You forget some (little) things. Not everything can be swapped out. Swap
> is extremly slow AND it is much worse to swapout/swapin programm code
> that should be run, instead of fetching some files from disk while the
> programm runs.
It's not always much worse, because as I explained, in my case, swap is 4-
way striped while most of the main system is only two-way striped. Thus,
that "irrelevant" stuff is relevant after all, because it alters the
conditions of the case in debate, because swap reads in at ~2x the speed
of most data read off disk including apps (which is itself ~2x what a
single-disk system might reasonably expect).
I've a feeling not appreciating this, not appreciating that your "test"
case example of compiling with 2 gigs RAM vs only 1 has little to do with
what might occur with PORTAGE_TMPDIR on tmpfs vs on disk, and not
appreciating the point RF and I are both trying to make, is due to the
same logic flaw.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-13 17:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 9:51 [gentoo-amd64] tmpfs help Beso
2008-02-12 10:21 ` Mateusz Mierzwinski
2008-02-12 10:37 ` Beso
2008-02-12 10:31 ` Pascal BERTIN
2008-02-12 10:47 ` Beso
2008-02-12 11:01 ` Pascal BERTIN
2008-02-12 11:25 ` Beso
2008-02-12 23:36 ` Mateusz Mierzwinski
2008-02-13 11:24 ` [gentoo-amd64] " Duncan
2008-02-13 12:46 ` Volker Armin Hemmann
2008-02-13 15:26 ` Richard Freeman
2008-02-13 17:22 ` Duncan [this message]
2008-02-13 19:27 ` Beso
2008-02-13 21:30 ` Duncan
2008-02-13 22:12 ` Mateusz Mierzwinski
2008-02-13 0:49 ` [gentoo-amd64] " Volker Armin Hemmann
2008-02-13 1:17 ` Richard Freeman
2008-02-13 3:04 ` Volker Armin Hemmann
2008-02-13 6:47 ` Steve Buzonas
2008-02-13 15:16 ` Richard Freeman
2008-02-13 16:17 ` Volker Armin Hemmann
2008-02-13 17:04 ` [gentoo-amd64] " Duncan
2008-02-13 19:42 ` [gentoo-amd64] " Richard Freeman
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=pan.2008.02.13.17.22.58@cox.net \
--to=1i5t5.duncan@cox.net \
--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