public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Concerns about WIPE_TMP change [offtopic]
Date: Sun, 20 Jan 2008 01:08:42 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.01.20.01.08.42@cox.net> (raw)
In-Reply-To: 47928523.2080203@xs4all.nl

Stefan de Konink <skinkie@xs4all.nl> posted 47928523.2080203@xs4all.nl,
excerpted below, on  Sun, 20 Jan 2008 00:17:55 +0100:

> ...very offtopic but how are you all compiling stuff like firefox on a
> ram disk. Or is 8GB of ram very cheap suddenly?

Well, tmpfs is swap-backed if necessary.  That's one of its strengths.  
And no, 8 gig of at least registered memory (what my Opterons use) isn't 
cheap -- I paid >$1000 for mine a year or so ago, but it sure is nice, 
combined with a dual dual-core system (Opteron 290s, upgraded ~4 months 
ago from 242s).

MAKEOPTS="-j20 -l12" keeps things from getting too out of hand.  It'll 
sometimes use 3 gigs or so of app memory (and about the same tmpfs it 
appears), but not too bad.  I ran -j (unlimited jobs) for awhile, and 
it's fun to see the jobs climb to several hundred, but even with 16 gigs 
4-way striped swap, the system goes draggy at that and >10 gigs into 
swap.  Keeping it to ~12 jobs means responsiveness stays reasonable, at 
least with the new 2.6.24 user based scheduling and the portage user kept 
to the same or half the share of my regular user.  Swap seldom gets used, 
and if it does, it's only a few megs of the apps I don't use much anyway 
(/proc/sys/vm/swappiness set to 100 so it flushes apps, not cache, to 
swap, as apps and the main system are on raid-6 so only two-way striped 
while swap is 4-way striped).

Nice system to run Gentoo on. =8^)  Using ccache, recompiling the updated 
kde4-svn daily is only ~2 hours or so, during which the system remains 
pleasantly usable. =8^)

-- 
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-dev@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-01-20  1:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19  1:48 [gentoo-dev] Concerns about WIPE_TMP change Stefan de Konink
2008-01-19  2:12 ` Mark Loeser
2008-01-19 12:55   ` Richard Freeman
2008-01-19 22:18     ` [gentoo-dev] " Duncan
2008-01-19 23:17       ` [gentoo-dev] Re: Concerns about WIPE_TMP change [offtopic] Stefan de Konink
2008-01-20  0:33         ` Alec Warner
2008-01-20  0:37           ` Stefan de Konink
2008-01-20  1:08         ` Duncan [this message]
2008-01-20 13:43         ` Richard Freeman
2008-01-22  1:34           ` Caleb Cushing
2008-01-22  2:54             ` Philip Webb
2008-01-24  7:06             ` Chris Gianelloni
2008-01-19 23:29       ` [gentoo-dev] Re: Concerns about WIPE_TMP change Olivier Galibert
2008-01-20  0:19         ` Ryan Hill
2008-01-20  1:23         ` Mike Frysinger
2008-01-20 13:47       ` Richard Freeman
2008-01-20 13:56         ` Fabian Groffen
2008-01-21  2:38         ` Donnie Berkholz
2008-01-21  5:05           ` Mike Frysinger
2008-01-21 21:42             ` Duncan
2008-01-19 11:05 ` [gentoo-dev] " Roy Marples
2008-01-19 20:54   ` Mike Frysinger
2008-01-19 21:03     ` Stefan de Konink
2008-01-19 21:26       ` Mike Frysinger
2008-01-19 21:33         ` Stefan de Konink

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.01.20.01.08.42@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@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