public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: tmpfs help
Date: Wed, 13 Feb 2008 17:04:42 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.02.13.17.04.41@cox.net> (raw)
In-Reply-To: 200802131717.57766.volker.armin.hemmann@tu-clausthal.de

Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de> posted
200802131717.57766.volker.armin.hemmann@tu-clausthal.de, excerpted below,
on  Wed, 13 Feb 2008 17:17:57 +0100:

> Not real benchmarks. But kdepim with enablefinal, 1gb of ram and -j2
> several hours. With j1 2h.
> .
> kdepim with 2gb of ram and j2 30m
> Just because first case swap storn, last case no swap at all.

But that's measuring the effect of the additional memory as much as it is 
the effect of swap.  What you need to do is kdepim with enablefinal, a 
gig of RAM and -j1 with PORTAGE_TMPDIR set to someplace on disk, against 
the same thing but with PORTAGE_TMPDIR set to a tmpfs of sufficient 
size.  Then and only then are you measuring the effect of tmpfs vs no 
tmpfs.  He (and I) are arguing that the tmpfs case will take less time 
because some files will get deleted before they end up being written to 
disk at all, as opposed to /all/ of them being written to disk (well, if 
they remain more than a few seconds anyway).

If you like you can of course do the test with -j2, but then you must use 
-j2 for both cases, so again PORTAGE_TMPDIR on tmpfs vs on disk is the 
only variable.

This of course assumes similar system load otherwise, presumably either 
an idle system (in X/GNOME/KDE/whatever both times or at the CLI both 
times) or only something steady, say streaming Internet radio, the same 
station at the same bits per second without visualizations, going on, 
with the same apps loaded in the background.  No answering mails or 
browsing or anything else interactive or variable since it's possible you 
could then be doing something different at a critical time in one case 
vs. the other.

-- 
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



  reply	other threads:[~2008-02-13 17:07 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
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           ` Duncan [this message]
2008-02-13 19:42           ` 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.04.41@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