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:  [OT] AGPART [SOLVED] DRIFT: RAM USAGE
Date: Sun, 6 May 2007 13:36:37 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.05.06.13.36.37@cox.net> (raw)
In-Reply-To: 20070506083444.279A29148B@mail.ilievnet.com

Daniel Iliev <danny@ilievnet.com> posted
20070506083444.279A29148B@mail.ilievnet.com, excerpted below, on  Sun, 06
May 2007 11:34:42 +0300:

> In case you didn't know...
> 
> There are several kernel configuration options you can tweak to make it
> cache more aggressively. Also you could try XFS - it is known to be one
> of the most hungry-for-RAM file systems. Please, have in mind that these
> tweaks could be dangerous for your file system in case of power failure.
> Consider using an UPS.

I knew about these in general, but still good to post as others may not.

You are talking write-caching here.  I generally leave that pretty much 
alone, for the reasons you mention (corruption in case of kernel panic 
and/or power failure).  That's also why I've chosen not to run XFS.  (I 
run reiserfs and while I did have issues some years ago, early kernel 
2.4, I've had none since the introduction of data=ordered journaling and 
that as the default, even when I had faulty memory and was having fairly 
regular kernel panics as a result.  I wouldn't have wanted to try that 
with big write caches and/or XFS!)

The caching I had in mind was read caching.  No risk there. =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-amd64@gentoo.org mailing list



      reply	other threads:[~2007-05-06 13:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 17:00 [gentoo-amd64] [OT] AGPART Daniel Iliev
2007-05-04 17:36 ` Jeffrey Gardner
2007-05-04 18:21   ` Wil Reichert
2007-05-04 18:47     ` Jeffrey Gardner
2007-05-05  1:58   ` [gentoo-amd64] " Duncan
2007-05-05  7:58 ` [gentoo-amd64] [OT] AGPART [SOLVED] Daniel Iliev
2007-05-05  9:15   ` [gentoo-amd64] " Duncan
2007-05-05  9:49     ` Peter Humphrey
2007-05-05 13:56     ` Boyd Stephen Smith Jr.
2007-05-06 14:36       ` [gentoo-amd64] Memory usage Was: " Duncan
2007-05-06  8:34     ` [gentoo-amd64] Re: [OT] AGPART [SOLVED] DRIFT: RAM USAGE Daniel Iliev
2007-05-06 13:36       ` Duncan [this message]

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.2007.05.06.13.36.37@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