public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Cc: MusicMan529@yahoo.com
Subject: Re: XFS mkfs/mount options (w/ better results this time)
Date: Tue, 24 Jun 2008 00:10:20 +0200	[thread overview]
Message-ID: <200806240010.20950.Martin@lichtvoll.de> (raw)
In-Reply-To: <200806232350.22161.Martin@lichtvoll.de>

Am Montag 23 Juni 2008 schrieb Martin Steigerwald:
> Am Montag 23 Juni 2008 schrieb Mark:
> > I ran a round of tests using 5 threads, to resemble 1 runnable and 1
> > waiting on each CPU, plus 1 more waiting. In other words, lightly
> > overloaded. XFS was the clear winner, with 378 MB/sec using the
> > "noop" scheduler. The "deadline" scheduler was a close second, with
> > 371 MB/sec.
> >
> > Here was the first twist: The completely fair queueing (CFQ)
> > scheduler seriously impeded XFS performance, so badly that even
> > "noop" out-performed it when the CPU was running at 40% clock.
>
> [...]
>
> > I re-ran all tests with 20 threads, to simulate severe process I/O
> > overloading. Even on my 2-CPU system, XFS scaled somewhat, achieving
> > 403 MB/sec with "deadline" and 401 MB/sec with "anticipatory." CFQ
> > didn't hurt the throughput as much this time, but it still came in
> > last (263 MB/sec).
>
> Thats interesting. I was curious and thus switched from cfq to deadline
> scheduler during parallel I/O workload on my ThinkPad T42 (aptitude
> upgrade / kmail receiving mails from POP3 account).
>
> It subjectively feeled way faster with deadline. I always wondered
> about the slowness of my ThinkPad T42 at massive parallel I/O. Now it
> feels a lot more responsive. Its as if I bought a new super-seek
> harddisk or what (compared to before).

It feels like I have a completely different system. Not only on massive 
parallel I/O. Starting OpenOffice... starting KDE apps... deadline seems 
to outperform cfq regarding subjectively perceived desktop performance to 
no end. That difference is absolutely astonishing for me. My ThinkPad 
*flies* compared to before.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

      reply	other threads:[~2008-06-23 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 18:05 XFS mkfs/mount options (w/ better results this time) Mark
2008-06-23 21:50 ` Martin Steigerwald
2008-06-23 22:10   ` Martin Steigerwald [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=200806240010.20950.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=MusicMan529@yahoo.com \
    --cc=linux-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