public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org,
	"Corrado Zoccolo" <czoccolo@gmail.com>,
	"\"J.A. Magallón\"" <jamagallon@ono.com>,
	"Jan Knutar" <jk-lkml@sci.fi>
Subject: Re: SSD and IO schedulers
Date: Thu, 09 Apr 2009 19:56:32 -0400	[thread overview]
Message-ID: <49DE8B30.3080208@tmr.com> (raw)
In-Reply-To: <20090408195610.GA5447@fancy-poultry.org>

Heinz Diehl wrote:
> On 08.04.2009, Corrado Zoccolo wrote: 
> 
>> I found that elevator=deadline performs much better than noop for
>> writes, and almost as well for reads
> [....]
> 
> The DL elevator has slightly more throughput than cfq and anticipatory,
> but is almost unusuable under load.
> 
> Running Theodore Ts'os "fsync-tester" while doing Linus' torture test 
> "while : ; do time sh -c "dd if=/dev/zero of=bigfile bs=8M count=256 ; sync; rm bigfile"; done"
> shows it clearly:
> 
This is good information, and if I ever configure a netbook for run fsync-tester 
I shall avoid the DL scheduler. ;-(

However... this test, and several others designed to find the ultimate 
performance limits of disk io, don't mimic any typical use of most desktops and 
virtually all netbooks.

Is there a benchmark which would return so useful data for typical use, doing 
some mail, some browsing, and maybe some light presentation, spreadsheet, or 
word processing. None of those uses are likely to generate this level of io, 
this file size, etc. The number of users is one, it's not used as a server, and 
probably most of the tuning done (if any) is aimed at battery life rather than 
blinding speed with a three digit load average.

I don't think this is a useful benchmark for netbooks, and hopefully there is a 
test available which will give more insight into the performance in typical use.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  parent reply	other threads:[~2009-04-09 23:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 21:55 SSD and IO schedulers Lorenzo Allegrucci
2009-01-31  8:45 ` Jens Axboe
2009-01-31 10:42   ` Alan Jenkins
2009-02-03 23:40 ` J.A. Magallón
2009-02-07 16:58   ` Jan Knutar
2009-04-08 19:18     ` Corrado Zoccolo
2009-04-08 19:56       ` Heinz Diehl
2009-04-08 20:18         ` Corrado Zoccolo
2009-04-09 10:33           ` Heinz Diehl
2009-04-09 10:50             ` Heinz Diehl
2009-04-09 23:56         ` Bill Davidsen [this message]
2009-04-10  5:57           ` Theodore Tso
2009-04-10 12:46             ` Bill Davidsen

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=49DE8B30.3080208@tmr.com \
    --to=davidsen@tmr.com \
    --cc=czoccolo@gmail.com \
    --cc=jamagallon@ono.com \
    --cc=jk-lkml@sci.fi \
    --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