From: Stian Jordet <liste@jordet.net>
To: David Sparks <dave@ca.sophos.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Extreme slowness with xfs [WAS: Re: Slowness with new pc]
Date: Tue, 25 Nov 2008 23:31:08 +0100 [thread overview]
Message-ID: <1227652268.10741.3.camel@chevrolet> (raw)
In-Reply-To: <492C75E2.1080701@ca.sophos.com>
ti., 25.11.2008 kl. 14.02 -0800, skrev David Sparks:
> > With no barriers, it's 22s faster than my workstation. That can't be the
> > way it's supposed to be?
>
> What IO elevator are you using? Did you try the 'noop' or 'deadline' schedulers?
>
> cat /sys/block/sda/queue/scheduler
> echo noop > /sys/block/sda/queue/scheduler
That improved the time 10s (noop and deadline both finished at 46s,
while cfq (still) uses 59...
Still slower than my laptop... (ok, I do understand that this is a very
static benchmark, that really doesn't say anything about real life
performance. But "everyone" unpacks the kernel faster than I, on a brand
new system worth $3500USD...
Thanks :)
-Stian
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-11-25 22:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1226760254.5089.11.camel@chevrolet>
[not found] ` <430c4fa50811180551r67d5d680tf1ffa493604ac4ea@mail.gmail.com>
2008-11-23 21:48 ` Extreme slowness with xfs [WAS: Re: Slowness with new pc] Stian Jordet
2008-11-23 22:25 ` Justin Piszcz
2008-11-24 0:19 ` Stian Jordet
2008-11-24 9:50 ` Justin Piszcz
2008-11-24 23:36 ` Stian Jordet
2008-11-24 23:52 ` Justin Piszcz
2008-11-25 0:09 ` Sven-Haegar Koch
2008-11-25 20:44 ` Stian Jordet
2008-11-25 21:22 ` Eric Sandeen
[not found] ` <1227649893.6557.10.camel@oldsmobile>
2008-11-25 22:02 ` David Sparks
2008-11-25 22:31 ` Stian Jordet [this message]
2008-11-25 1:36 ` Eric Sandeen
[not found] ` <1227647010.7992.34.camel@chevrolet>
2008-11-26 12:30 ` Martin Steigerwald
2008-11-26 21:43 ` Dave Chinner
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=1227652268.10741.3.camel@chevrolet \
--to=liste@jordet.net \
--cc=dave@ca.sophos.com \
--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