linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: linux-kernel@vger.kernel.org
Cc: "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, 9 Apr 2009 12:33:22 +0200	[thread overview]
Message-ID: <20090409103322.GA5382@fancy-poultry.org> (raw)
In-Reply-To: <4e5e476b0904081318h4445556am1a6b0a49c6175719@mail.gmail.com>

On 08.04.2009, Corrado Zoccolo wrote: 

> Well, that's not an usual workload for netbooks, where most SSDs are
> currently deployed.

Yes, that's right.

> For usual workloads, that are mostly read, cfq has lower performance
> both in throughput and in latency than deadline.

I don't have a netbook myself, but a Notebook with a singlecore
Intel M-530 CPU and an SSD harddisk, hdparm says:

[....]
ATA device, with non-removable media
Model Number:       OCZ SOLID_SSD
Serial Number:      MK0708520E8AA000B
Firmware Revision:  02.10104
[....]

I did run a short test with fsync-tester, running 10 read-processes
on the disk at the same time. The results between CFQ and DL don't differ
visibly. Maybe I don't get the point, or my tests simply suck, 
but with these results in mind, and considering the fact that when 
the load gets gradually higher, DL will lead to hickups up to ca. 10 secs, 
I would say that DL sucks _bigtime_ , compared to CFQ. 
(Throughput doesn't differ that much either..).


CFQ:

fsync time: 0.0209
fsync time: 0.0204
fsync time: 0.2026
fsync time: 0.2053
fsync time: 0.2036
fsync time: 0.2348
fsync time: 0.2030
fsync time: 0.2051
fsync time: 0.2024
fsync time: 0.2108
fsync time: 0.2025
fsync time: 0.2025
fsync time: 0.2030
fsync time: 0.2006
fsync time: 0.2368
fsync time: 0.2070
fsync time: 0.2009
fsync time: 0.2033
fsync time: 0.2101
fsync time: 0.2054
fsync time: 0.2028
fsync time: 0.2031
fsync time: 0.2073
fsync time: 0.2100
fsync time: 0.2078
fsync time: 0.2093
fsync time: 0.0275
fsync time: 0.0217
fsync time: 0.0298
fsync time: 0.0206
fsync time: 0.0184
fsync time: 0.0201
fsync time: 0.0169
fsync time: 0.0202
fsync time: 0.0186
fsync time: 0.0224
fsync time: 0.0224
fsync time: 0.0214
fsync time: 0.0246

DL

fsync time: 0.0296
fsync time: 0.0223
fsync time: 0.0262
fsync time: 0.0232
fsync time: 0.0230
fsync time: 0.0235
fsync time: 0.0187
fsync time: 0.0284
fsync time: 0.0227
fsync time: 0.0314
fsync time: 0.0236
fsync time: 0.0251
fsync time: 0.0221
fsync time: 0.0279
fsync time: 0.0244
fsync time: 0.0217
fsync time: 0.0248
fsync time: 0.0241
fsync time: 0.0229
fsync time: 0.0212
fsync time: 0.0243
fsync time: 0.0227
fsync time: 0.0257
fsync time: 0.0206
fsync time: 0.0214
fsync time: 0.0255
fsync time: 0.0213
fsync time: 0.0212
fsync time: 0.0266
fsync time: 0.0221
fsync time: 0.0212
fsync time: 0.0246
fsync time: 0.0208
fsync time: 0.0267
fsync time: 0.0220
fsync time: 0.0213
fsync time: 0.0212
fsync time: 0.0264


htd@wildsau:~> bonnie++ -u htd:default -d /testing -s 4004m -m wildsau -n 16:100000:16:64

CFQ

Version 1.01d       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
wildsau     16016M 79619  45 78058  14 28841   7 98629  61 138596  14  1292   3
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files:max:min        /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
    16:100000:16/64   594   7 +++++ +++  1309   6   556   6 +++++ +++   449   4


DL

Version 1.01d       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine       Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec  %CP  /sec %CP
wildsau     16016M 80619  47 78123  14 27842   7 96317  59 135446  14  1383   4
                    ------Sequential Create------ --------Random Create--------
                    -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
files:max:min        /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
    16:100000:16/64   601   8 +++++ +++  1288   6   546   6 +++++ +++   432   4




  reply	other threads:[~2009-04-09 10:31 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 [this message]
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=20090409103322.GA5382@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --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;
as well as URLs for NNTP newsgroup(s).