All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cami <camis@mweb.co.za>
To: reiserfs-list@namesys.com
Subject: Re: reiserfs v3 patches updated
Date: Tue, 06 Apr 2004 22:51:56 +0200	[thread overview]
Message-ID: <4073186C.3010601@mweb.co.za> (raw)
In-Reply-To: <1081283607.30811.206.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..
> 
> 
> I'm a little slow today.  data=ordered is the default with these
> patches.  You need to mount -o data=writeback.

data=writeback yields pretty much the same iowait results..
(machine 1+2 are around 5%->8% whereas machine 3->8 are at around 0.8%)

Cami


  reply	other threads:[~2004-04-06 20:51 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
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 [this message]
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=4073186C.3010601@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.