All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: "Benjamin S." <sbenni@gmx.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: bad performance with SSD since kernel version 2.6.32
Date: Sat, 20 Feb 2010 12:35:00 -0600	[thread overview]
Message-ID: <4B802B54.1080009@gmail.com> (raw)
In-Reply-To: <20100220142826.62dd5989@pluto-lenny.milky.way>

On 02/20/2010 07:28 AM, Benjamin S. wrote:
>
> Hello list,
>
> I have a Super Talent Ultradrive GX MLC 64GB SSD and an Intel
> DH55HC board with H55 chipset. Processor is an Intel Core i5-661.
>
> Since 2.6.32 the sequentiell read performance of the ssd is bad:
>
> # dd if=/dev/sda of=/dev/zero bs=1M count=300
> 300+0 records in
> 300+0 records out
> 314572800 bytes (315 MB) copied, 4.61777 s, 68.1 MB/s
>
> Same results with other blocksizes (e.g tested with 4K).
>
>
> With 2.6.31.7 the same hardware is able to read with about
> 190MB/s.
>
>
> The normal hard drive reads with both kernel versions with about 100MB/s.
>
>
> Does somebody have an idea what I can test before I have to bisect
> it?

Could be some kind of block layer or IO scheduler behavior change.. you 
could try testing after doing:

echo noop > /sys/block/sda/queue/scheduler

or

echo deadline > /sys/block/sda/queue/scheduler

and see if that affects the speed..

  reply	other threads:[~2010-02-20 18:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 13:28 bad performance with SSD since kernel version 2.6.32 Benjamin S.
2010-02-20 18:35 ` Robert Hancock [this message]
2010-02-21  1:26   ` Benjamin S.
     [not found]     ` <51f3faa71002210922i542c37f0j9e0e4a84d0977f90@mail.gmail.com>
     [not found]       ` <20100221225544.5a9ded51@pluto-lenny.milky.way>
     [not found]         ` <51f3faa71002211400u2177660ei1c0dc3d9306b146e@mail.gmail.com>
2010-02-22 13:18           ` Benjamin S.
2010-02-22 14:41             ` Robert Hancock
2010-02-22 19:05             ` Jens Axboe
2010-02-22 20:25               ` Benjamin S.
2010-02-23  6:22                 ` Jens Axboe
2010-02-22 21:49               ` Mark Lord
2010-02-22 23:22                 ` Robert Hancock
2010-02-23  6:21                   ` Jens Axboe
2010-02-24 15:09                     ` Mark Lord
2010-02-24 15:34                       ` Jens Axboe
2010-02-24 15:48                         ` Mark Lord
2010-02-24 19:05                           ` Jens Axboe

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=4B802B54.1080009@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sbenni@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.