From: Emmanuel Florac <eflorac@intellique.com>
To: Andrew Clayton <andrew@digital-domain.net>
Cc: xfs@oss.sgi.com
Subject: Re: Latencies in XFS.
Date: Sun, 14 Oct 2007 16:49:23 +0200 [thread overview]
Message-ID: <20071014164923.083d55dd@galadriel.home> (raw)
In-Reply-To: <20071014012323.1d6c9e8e@alpha.digital-domain.net>
Le Sun, 14 Oct 2007 01:23:23 +0100 vous écriviez:
> > I notice you use a bleeding-edge unstable kernel, with a whole new
> > scheduler. I tried your benchmark on a machine running a known
> > stable kernel (2.6.20.17) and the slowdown is similar in xfs and
> > other fs.
>
> I don't see the slowdown in ext3.
I tried it and the slowdown is proportionnally similar, though XFS is
slower IO-wise.
--
--------------------------------------------------
Emmanuel Florac www.intellique.com
--------------------------------------------------
prev parent reply other threads:[~2007-10-14 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 15:36 Latencies in XFS Andrew Clayton
2007-10-13 15:35 ` Peter Grandi
2007-10-13 18:10 ` Emmanuel Florac
2007-10-14 0:23 ` Andrew Clayton
2007-10-14 14:49 ` Emmanuel Florac [this message]
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=20071014164923.083d55dd@galadriel.home \
--to=eflorac@intellique.com \
--cc=andrew@digital-domain.net \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox