public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Martin MOKREJ? <mmokrejs@ribosome.natur.cuni.cz>
Cc: linux-xfs@oss.gi.com, linux-kernel@vger.kernel.org
Subject: Re: Filesystem performance on 2.4.28-pre3 on hardware RAID5.
Date: Fri, 29 Oct 2004 17:31:48 +1000	[thread overview]
Message-ID: <20041029073148.GG1246@frodo> (raw)
In-Reply-To: <41817612.2020104@ribosome.natur.cuni.cz>

Hi there,

On Fri, Oct 29, 2004 at 12:43:30AM +0200, Martin MOKREJ? wrote:
> "mount -t xfs -o async" unexpectedly kills random seek performance,
> but is still a bit better than with "-o sync". ;) Maybe it has to do
> with the dramatic jump in CPU consumption of this operation,
> as it in both cases it takes about 21-26% instead of usual 3%.
> Why? Isn't actually async default mode?

Thats odd.  Actually, I'm not sure what the "async" option is meant
to do, it isn't seen by the fs afaict (XFS isn't looking for it)... 
we also use the generic_file_llseek code in XFS ... so we're not
doing anything special there either -- some profiling data showing
where that CPU time is spent would be insightful.

> Sequential create /Create
> Random create /Create
> XFS             60-120 ms

You may get better results using a version 2 log (mkfs option)
with large in-core log buffers (mount option) for these (which
mkfs version are you using atm?)

cheers.

-- 
Nathan

  reply	other threads:[~2004-10-29  7:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28 22:43 Filesystem performance on 2.4.28-pre3 on hardware RAID5 Martin MOKREJŠ
2004-10-29  7:31 ` Nathan Scott [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-29 11:10 mmokrejs
2004-10-31 23:24 ` Nathan Scott
     [not found]   ` <418574FB.2020907@ribosome.natur.cuni.cz>
     [not found]     ` <20041031223214.GB690@frodo>
     [not found]       ` <41878432.5060904@ribosome.natur.cuni.cz>
2004-11-03  0:17         ` Nathan Scott

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=20041029073148.GG1246@frodo \
    --to=nathans@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.gi.com \
    --cc=mmokrejs@ribosome.natur.cuni.cz \
    /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