From: camis <camis@mweb.co.za>
To: reiserfs-list@namesys.com
Subject: Re: reiserfs v3 patches updated
Date: Tue, 06 Apr 2004 21:53:33 +0200 [thread overview]
Message-ID: <40730ABD.3070507@mweb.co.za> (raw)
In-Reply-To: <1081279465.30829.128.camel@watt.suse.com>
>>The majority of the rest of the machines iowait hover around the 1%
>>mark.. CPU time tends to be about the same, just the iowait is much
>>much higher..
>
> Very interesting. data=ordered makes fsync more expensive, since it
> ends up syncing more then just the buffers for that one file. Could you
> please try removing data=ordered from machine1?
Ok.. after leaving it for a few minutes..
machine 1: (mounted:
noatime,nodiratime,alloc=skip_busy:dirid_groups,packing_groups)
21:48:08 up 12:49, 1 user, load average: 0.57, 0.74, 0.92
338 processes: 337 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 9.6% 0.0% 39.2% 0.0% 1.2% 6.8% 342.0%
cpu00 2.2% 0.0% 12.4% 0.1% 0.7% 1.3% 82.9%
cpu01 2.6% 0.0% 9.1% 0.0% 0.1% 1.9% 86.0%
cpu02 2.4% 0.0% 9.0% 0.0% 0.0% 0.9% 87.5%
cpu03 2.6% 0.0% 8.9% 0.0% 0.0% 2.6% 85.6%
At first i thought that it *might* be just this machine itself,
so i rebooted machine2 with the same kernel patches..
machine 2: (mounted:
noatime,nodiratime,alloc=skip_busy:dirid_groups,packing_groups)
21:46:24 up 7 min, 1 user, load average: 0.85, 0.64, 0.27
315 processes: 314 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 9.6% 0.0% 34.8% 0.0% 1.2% 7.2% 346.4%
cpu00 2.5% 0.0% 7.1% 0.1% 1.1% 2.1% 86.8%
cpu01 2.6% 0.0% 8.0% 0.0% 0.1% 1.1% 87.8%
cpu02 2.4% 0.0% 10.9% 0.0% 0.1% 1.7% 84.6%
cpu03 2.1% 0.0% 8.6% 0.0% 0.0% 2.3% 86.8%
machine 3->8: (mounted: noatime,nodiratime)
21:46:21 up 1 day, 9:12, 1 user, load average: 1.07, 2.24, 1.88
295 processes: 294 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 11.2% 0.0% 40.8% 0.0% 2.0% 1.6% 343.2%
cpu00 2.7% 0.0% 10.4% 0.1% 1.5% 0.3% 84.7%
cpu01 3.0% 0.0% 10.1% 0.0% 0.1% 0.5% 85.9%
cpu02 2.6% 0.0% 11.1% 0.0% 0.1% 0.5% 85.3%
cpu03 2.8% 0.0% 9.2% 0.0% 0.1% 0.3% 87.2%
What i then tried on machine1 was remounting it noatime,nodiratime and
what was wierd was that the iowait stayed exactly the same, no indication
of dropping at all.. Does the kernel patches change any of the default
mount options at all? If i put the stock 2.6.5 kernel back on without
the patch applied and mount it back as noatime,nodiratime, the iowait
drops back to its normal 1%..
Cami
next prev parent reply other threads:[~2004-04-06 19:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 0:10 reiserfs v3 patches updated Chris Mason
2004-04-06 16:38 ` Christian Mayrhuber
2004-04-06 16:48 ` Chris Mason
2004-04-06 18:29 ` camis
2004-04-06 18:47 ` Chris Mason
2004-04-06 19:17 ` camis
2004-04-06 19:24 ` Chris Mason
2004-04-06 19:53 ` camis [this message]
2004-04-06 20:29 ` Chris Mason
2004-04-06 20:38 ` Cami
2004-04-06 20:33 ` Chris Mason
2004-04-06 20:51 ` Cami
2004-04-06 21:10 ` Chris Mason
2004-04-06 21:30 ` Cami
2004-04-06 21:39 ` Chris Mason
2004-04-07 9:28 ` reiserfs v3 patches updated - Bug Christian Mayrhuber
2004-04-07 13:07 ` Chris Mason
[not found] ` <200404071714.39187.christian.mayrhuber@gmx.net>
2004-04-07 23:58 ` Chris Mason
2004-04-13 14:57 ` Christian Mayrhuber
2004-04-10 22:53 ` reiserfs v3 patches updated Hubert Chan
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=40730ABD.3070507@mweb.co.za \
--to=camis@mweb.co.za \
--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.