From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Weird XFS slowness
Date: Sun, 21 Jan 2007 02:29:53 +0200 [thread overview]
Message-ID: <200701210229.53179.caglar@pardus.org.tr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
Hi;
After switching ext3 to xfs, i realize system starts to _really_ unresponsive
and extracting tarballs, copying or deleting files or checking out svn
repositories are really slow, so i basically try to measure some for both xfs
and ext3 with same computer, same kernel (2.6.18.6), same disk, here are the
results
* between all tests i dropped caches
* i already tried to change block device's scheduler to as, noop and cfq,
nothing really changes
* i already tried 2.6.20-rc5 and 2.6.20-rc5.1.rt8.0085 which Ingo provides but
again nothing really changes
Kernel Tarball
--------------
a) XFS
ekin@idaho ~ $ time tar xvf linux-2.6.19.tar.bz2
...
real 2m16.865s
user 0m21.113s
sys 0m2.426s
b) EXT3
ekin@idaho ~ $ time tar xvf linux-2.6.19.tar.bz2
...
real 0m34.192s
user 0m20.624s
sys 0m1.771s
Deletion
--------
a) XFS
ekin@idaho ~ $ time rm -rf linux-2.6.19/
real 0m50.902s
user 0m0.064s
sys 0m1.378s
b) EXT3
ekin@idaho ~ $ time rm -rf linux-2.6.19/
real 0m1.162s
user 0m0.031s
sys 0m0.411s
Copying
-------
a) XFS
ekin@idaho test $ time cp -r ../linux-2.6.19 .
...
real 1m42.833s
user 0m0.124s
sys 0m2.621s
b) EXT3
ekin@idaho test $ time cp -r ../linux-2.6.19 .
...
real 0m38.456s
user 0m0.166s
sys 0m2.744s
I'm not sure these are normal numbers or its a regression (i'm just starting
to use XFS) so any hints will be appreciated.
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-01-21 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 0:29 S.Çağlar Onur [this message]
2007-01-21 21:33 ` Jan Engelhardt
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=200701210229.53179.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome