public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: markus <markus@kola.li>
To: Purush Gupta <purush.gupta@nutanix.com>
Cc: Nagalakshmi Nandigama <Nagalakshmi.Nandigama@lsi.com>,
	Sreekanth Reddy <Sreekanth.Reddy@lsi.com>,
	support@lsi.com, DL-MPTFusionLinux@lsi.com,
	linux-scsi@vger.kernel.org,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Slow I/O performance on SAS1064
Date: Sat, 8 Mar 2014 21:14:50 +0100	[thread overview]
Message-ID: <20140308201450.GA18581@localhost.localdomain> (raw)
In-Reply-To: <CAN7X1Umb_wyTCk9w590AnSTFgL=3CC5x8zGNiGZoAdNEej9TCQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

On Fri, Mar 07, 2014 at 08:24:48AM -0800, Purush Gupta wrote:
> I noticed you had benchmarked only sda target, is the behavior same on
> other targets?
> 
Yes the other disk are equal to sda , but they are used with zfs and there were other preformance problems because of the multible disk access.
config:

        NAME        STATE     READ WRITE CKSUM
        home        ONLINE       0     0     0
          raidz1-0  ONLINE       0     0     0
            sdb     ONLINE       0     0     3
            sdc     ONLINE       0     0     0
            sdd     ONLINE       0     0     0



> Since they are SCSI targets, have you explored sg_utils [
> http://sg.danny.cz/sg/uu_index.html]
> 
> And for benchmarking I also recommend FIO https://github.com/axboe/fio
> 
Thanks for the tips.
> Good luck,
> Purush
> 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

       reply	other threads:[~2014-03-08 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN7X1Umb_wyTCk9w590AnSTFgL=3CC5x8zGNiGZoAdNEej9TCQ@mail.gmail.com>
2014-03-08 20:14 ` markus [this message]
2014-03-05 17:50 Slow I/O performance on SAS1064 Markus
2014-03-05 18:21 ` Mark Knecht
2014-03-05 21:40   ` markus
2014-03-06 20:51     ` Mark Knecht
2014-03-07  9:46       ` markus

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=20140308201450.GA18581@localhost.localdomain \
    --to=markus@kola.li \
    --cc=DL-MPTFusionLinux@lsi.com \
    --cc=Nagalakshmi.Nandigama@lsi.com \
    --cc=Sreekanth.Reddy@lsi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=purush.gupta@nutanix.com \
    --cc=support@lsi.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