Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Joe Landman <landman@scalableinformatics.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: fio@vger.kernel.org
Subject: Re: An issue with fio performance on an SSD
Date: Mon, 19 Jul 2010 13:44:55 -0400	[thread overview]
Message-ID: <4C448F17.9050309@scalableinformatics.com> (raw)
In-Reply-To: <20100719174049.GA32503@redhat.com>

Vivek Goyal wrote:
> On Mon, Jul 19, 2010 at 01:25:06PM -0400, Joe Landman wrote:
>> Joe Landman wrote:
>>> Greetings
>>>
>>>  We are playing with some SSDs, and as usual, we want to use fio
>>> for our testing regime.  So we set up a simple streaming write:
>> Ok, I figured it out.
>>
>> Add zero_buffers=1 to the job specification.  Then we get this:
>>
>> Run status group 0 (all jobs):
>>   WRITE: io=32,706MB, aggrb=535MB/s, minb=548MB/s, maxb=548MB/s,
>> mint=61133msec, maxt=61133msec
> 
> Interesting. Why not initializing bufferes with zero leads to poor
> performance?

I think this is an SSD controller compression issue.  That is, the 
Sandforce controllers want to do compression of some sort on the data. 
So if we start out with truly random data, which doesn't get good 
compression ratios, we get not so good performance.

Joe

-- 
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: landman@scalableinformatics.com
web  : http://scalableinformatics.com
        http://scalableinformatics.com/jackrabbit
phone: +1 734 786 8423 x121
fax  : +1 866 888 3112
cell : +1 734 612 4615

      reply	other threads:[~2010-07-19 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 14:58 An issue with fio performance on an SSD Joe Landman
2010-07-19 17:25 ` Joe Landman
2010-07-19 17:40   ` Vivek Goyal
2010-07-19 17:44     ` Joe Landman [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=4C448F17.9050309@scalableinformatics.com \
    --to=landman@scalableinformatics.com \
    --cc=fio@vger.kernel.org \
    --cc=vgoyal@redhat.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