public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Lorenzo Allegrucci <l.allegrucci@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SSD and IO schedulers
Date: Sat, 31 Jan 2009 09:45:58 +0100	[thread overview]
Message-ID: <20090131084558.GV30821@kernel.dk> (raw)
In-Reply-To: <4dcf7d360901301355l7ed26a5aob7ef6d79d9607b6b@mail.gmail.com>

On Fri, Jan 30 2009, Lorenzo Allegrucci wrote:
> Hi, I was wondering how IO schedulers such as as-iosched, deadline and
> cfq behave on SSD
> (that have virtually no seek time), from a theoretical point of view.
> How do they affect
> performance on these devices?
> I heard that the noop scheduler is often chosen by owners of EeePcs
> (with a SSD unit).
> They report superior performance by using this (quite simple) scheduler.
> Are there any scientific benchmarks around?

Just recently the io schedulers started checking for SSD devices, so
today it should not matter performance wise (throughput) whether you use
CFQ or NOOP on eg the eeepc. The io scheduler is still quite important
for providing fair access to the device, especially on the cheaper end
of the SSD segment.

-- 
Jens Axboe


  reply	other threads:[~2009-01-31  8:47 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 [this message]
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
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=20090131084558.GV30821@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=l.allegrucci@gmail.com \
    --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