From: Tom Vier <tmv@comcast.net>
To: reiserfs-list@namesys.com
Subject: Re: reiser4: first impression (vs xfs and jfs)
Date: Wed, 7 Jun 2006 13:58:28 -0400 [thread overview]
Message-ID: <20060607175828.GA4670@zero> (raw)
In-Reply-To: <1149604706.6389.40.camel@tribesman.namesys.com>
On Tue, Jun 06, 2006 at 06:38:26PM +0400, Vladimir V. Saveliev wrote:
> reiser4 has an option for that.
> mount -o tmgr.atom_max_age=N
> N is decimal number of seconds. Changes older than N will be forced to
> commit.
Unfortunetly, this causes even more read pauses from the source, when
running rsync. I also tried cpio (-p mode) and cp -a, same pauses. When
syncing, r4 seems to have about a 5 second pause, then a burst of seeks and
writes. I also tried disabling clock throttling, no difference. I have a
fast system. Two single core 2.6ghz opterons. CPU time during the pause
after sync and before the writes doesn't seem to very high. I thought r4
might be cpu bound, but it doesn't seem to be. I'm not sure what's causing
this pause. If i had more free time, i'd setup kernel profiling.
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
next prev parent reply other threads:[~2006-06-07 17:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 15:51 reiser4: first impression (vs xfs and jfs) Tom Vier
2006-05-23 19:08 ` Gregory Maxwell
2006-05-23 19:13 ` Alexey Polyakov
[not found] ` <20060523201712.GD25889@zero>
2006-05-23 21:00 ` Alexey Polyakov
2006-06-06 13:44 ` Tom Vier
2006-06-06 14:38 ` Vladimir V. Saveliev
2006-06-06 15:30 ` Clay Barnes
2006-06-06 17:47 ` PFC
2006-06-06 19:26 ` Hans Reiser
2006-06-07 17:21 ` PFC
2006-06-06 19:25 ` Hans Reiser
2006-06-07 0:13 ` Clay Barnes
2006-06-07 0:42 ` Hans Reiser
2006-06-08 0:55 ` Nate Diller
2006-06-08 14:18 ` Tom Vier
2006-06-08 14:06 ` Tom Vier
2006-06-09 8:05 ` Hans Reiser
2006-06-07 17:58 ` Tom Vier [this message]
2006-06-08 0:41 ` Nate Diller
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=20060607175828.GA4670@zero \
--to=tmv@comcast.net \
--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.