From: David Masover <ninja@slaphack.com>
To: Clemens Eisserer <linuxhippy@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Howto make reiser-3.6 a bit more standby friendly?
Date: Tue, 23 Aug 2005 09:25:40 -0500 [thread overview]
Message-ID: <430B31E4.6080807@slaphack.com> (raw)
In-Reply-To: <194f6255050823065872f42089@mail.gmail.com>
Clemens Eisserer wrote:
> Hello David and thanks a lot for answering my question.
>
>
>>Have you tried "-o noatime"?
>
> Why do you think this could help?
> Since the machine does absolutly nothing (no services, simply nothing
> than a open bash).
I remember someone explaining this before. It went something like this:
The atime update happens whenever something is accessed. Something
(/bin/atime? not on my system) needs to be accessed in order to make
that update. So, every five seconds, there _will_ be a new atime that
must be written, and since ReiserFS3 doesn't do lazy writes, it _will_
be flushed out to disk. (Reiser4 would just keep it in RAM until memory
pressure or a sync/fsync forced it out to disk.)
So, the simplest way is to do "-a noatime", unless you really need the
atime updates. It'll boost your performance, too...
But this is all from memory, from a long time ago. I have no idea if
any of the above is still true.
>>Also, Reiser4 is much more standby-friendly. If you've got the RAM, it
>>won't touch your disk too much.
>
> Yes I know - but its a bit too complicated for me to get everything
> up&running from ground up using Reiser4 since its not in the
> default-kernel of debian :-(
Nor Gentoo, but I use it there anyway.
next prev parent reply other threads:[~2005-08-23 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 12:39 Howto make reiser-3.6 a bit more standby friendly? Clemens Eisserer
2005-08-23 13:37 ` David Masover
2005-08-23 13:58 ` Clemens Eisserer
2005-08-23 14:25 ` David Masover [this message]
2005-08-23 15:51 ` Clemens Eisserer
2005-08-23 16:10 ` David Masover
2005-08-23 16:38 ` Christian Iversen
2005-08-23 19:10 ` Clemens Eisserer
2005-08-23 14:21 ` Jonathan Briggs
2005-08-23 22:16 ` Pierre Etchemaïté
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=430B31E4.6080807@slaphack.com \
--to=ninja@slaphack.com \
--cc=linuxhippy@gmail.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.