public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: scst-devel <scst-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Scst-devel] ISCSI-SCST performance (with also IET and STGT	data)
Date: Fri, 17 Apr 2009 22:11:09 +0400	[thread overview]
Message-ID: <49E8C63D.8090901@vlnb.net> (raw)
In-Reply-To: <e2e108260904040104u37953ef7x74b8713dfcf3166a@mail.gmail.com>

Bart Van Assche, on 04/04/2009 12:04 PM wrote:
> On Thu, Apr 2, 2009 at 7:16 PM, Vladislav Bolkhovitin <vst@vlnb.net> wrote:
>> Bart Van Assche, on 04/02/2009 12:14 AM wrote:
>>> I have repeated some of these performance tests for iSCSI over IPoIB
>>> (two DDR PCIe 1.0 ConnectX HCA's connected back to back). The results
>>> for the buffered I/O test with a block size of 512K (initiator)
>>> against a file of 1GB residing on a tmpfs filesystem on the target are
>>> as follows:
>>>
>>> write-test: iSCSI-SCST 243 MB/s; IET 192 MB/s.
>>> read-test: iSCSI-SCST 291 MB/s; IET 223 MB/s.
>>>
>>> And for a block size of 4 KB:
>>>
>>> write-test: iSCSI-SCST 43 MB/s; IET 42 MB/s.
>>> read-test: iSCSI-SCST 288 MB/s; IET 221 MB/s.
>> Do you have any thoughts why writes are so bad? It shouldn't be so..
> 
> By this time I have run the following variation of the 4 KB write test:
> * Target: iSCSI-SCST was exporting a 1 GB file residing on a tmpfs filesystem.
> * Initiator: two processes were writing 4 KB blocks as follows:
> dd if=/dev/zero of=/dev/sdb bs=4K seek=0 count=131072 oflag=sync &
> dd if=/dev/zero of=/dev/sdb bs=4K seek=131072 count=131072 oflag=sync &
> 
> Results:
> * Each dd process on the initiator was writing at a speed of 37.8
> MB/s, or a combined writing speed of 75.6 MB/s.
> * CPU load on the initiator system during the test: 2.0.
> * According to /proc/interrupts, about 38000 mlx4-comp-0 interrupts
> were triggered per second.
> 
> These results confirm that the initiator system was the bottleneck
> during the 4 KB write test, not the target system.

If so with oflag=direct you should have a performance gain, because you 
will eliminate a data copy.

> Bart.
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Scst-devel mailing list
> Scst-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scst-devel
> 


      reply	other threads:[~2009-04-17 18:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 17:33 ISCSI-SCST performance (with also IET and STGT data) Vladislav Bolkhovitin
     [not found] ` <e2e108260903301106y2b750c23kfab978567f3de3a0@mail.gmail.com>
2009-03-30 18:33   ` [Scst-devel] " Vladislav Bolkhovitin
2009-03-30 18:53     ` Bart Van Assche
2009-03-31 17:37       ` Vladislav Bolkhovitin
2009-03-31 18:43         ` [Iscsitarget-devel] [Scst-devel] ISCSI-SCST performance (withalso " Ross S. W. Walker
2009-04-01  6:29           ` Bart Van Assche
2009-04-01 12:20             ` Ross Walker
2009-04-01 20:23               ` James Bottomley
2009-04-02  7:38                 ` [Scst-devel] [Iscsitarget-devel] ISCSI-SCST performance (with also " Vladislav Bolkhovitin
2009-04-02  9:02                   ` Vladislav Bolkhovitin
2009-04-02 14:06                     ` Ross S. W. Walker
2009-04-02 14:14                       ` Ross S. W. Walker
2009-04-02 15:36                       ` Vladislav Bolkhovitin
2009-04-02 17:19                         ` Ross S. W. Walker
2009-04-01 20:14 ` Bart Van Assche
2009-04-02 17:16   ` [Scst-devel] " Vladislav Bolkhovitin
2009-04-03 17:08     ` Bart Van Assche
2009-04-03 17:13       ` [Scst-devel] ISCSI-SCST performance (with also IET and STGTdata) Sufficool, Stanley
2009-04-03 17:52         ` Bart Van Assche
2009-04-04  8:04     ` [Scst-devel] ISCSI-SCST performance (with also IET and STGT data) Bart Van Assche
2009-04-17 18:11       ` Vladislav Bolkhovitin [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=49E8C63D.8090901@vlnb.net \
    --to=vst@vlnb.net \
    --cc=bart.vanassche@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    /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