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: Thu, 02 Apr 2009 21:16:17 +0400 [thread overview]
Message-ID: <49D4F2E1.7000507@vlnb.net> (raw)
In-Reply-To: <e2e108260904011314h1e0cf5c5wcdf210eee24d40d8@mail.gmail.com>
Bart Van Assche, on 04/02/2009 12:14 AM wrote:
> On Mon, Mar 30, 2009 at 7:33 PM, Vladislav Bolkhovitin <vst@vlnb.net> wrote:
> ==================================================================
>> I. SEQUENTIAL ACCESS OVER SINGLE LINE
>>
>> 1. # dd if=/dev/sdX of=/dev/null bs=512K count=2000
>>
>> ISCSI-SCST IET STGT
>> NULLIO: 106 105 103
>> FILEIO/CFQ: 82 57 55
>> FILEIO/deadline 69 69 67
>> BLOCKIO/CFQ 81 28 -
>> BLOCKIO/deadline 80 66 -
>
> 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..
> Or: depending on the test scenario, SCST transfers data between 2% and
> 30% faster via the iSCSI protocol over this network.
>
> Something that is not relevant for this comparison, but interesting to
> know: with the SRP implementation in SCST the maximal read throughput
> is 1290 MB/s on the same setup.
This can be well explained. The limiting factor for iSCSI is that
iSCSI/TCP processing overloads a single CPU core. You can prove that on
vmstat output during the test. Sum of user and sys time should be about
100/(number of CPUs) or higher. SRP has a lot more CPU effective, hence
better has throughput.
If you try to test with 2 or more parallel IO streams, you should have
the correspondingly increased aggregate throughput up to the moment you
hit your memory copy bandwidth.
Thanks,
Vlad
> Bart.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Scst-devel mailing list
> Scst-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scst-devel
>
next prev parent reply other threads:[~2009-04-02 17:16 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 ` Vladislav Bolkhovitin [this message]
2009-04-03 17:08 ` [Scst-devel] " 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
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=49D4F2E1.7000507@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