From: Vladislav Bolkhovitin <vst-d+Crzxg7Rs0@public.gmane.org>
To: Robin Humble <robin.humble+stgt-FCV4sgi5zeUQrrorzV6ljw@public.gmane.org>
Cc: FUJITA Tomonori
<fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>,
stgt-devel-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org,
scst-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Performance of SCST versus STGT
Date: Thu, 24 Jan 2008 15:40:24 +0300 [thread overview]
Message-ID: <47988738.5090000@vlnb.net> (raw)
In-Reply-To: <20080124113215.GB26751-Td5ZOp7sT3Xw02mFwxTg32+DJq1SqhBbsOSz5zK2v9k@public.gmane.org>
Robin Humble wrote:
> On Thu, Jan 24, 2008 at 11:36:45AM +0100, Bart Van Assche wrote:
>
>>On Jan 24, 2008 8:06 AM, Robin Humble <robin.humble+stgt-FCV4sgi5zeUQrrorzV6ljw@public.gmane.org> wrote:
>>
>>>On Tue, Jan 22, 2008 at 01:32:08PM +0100, Bart Van Assche wrote:
>>>
>>>>.............................................................................................
>>>>. . STGT read SCST read . STGT read SCST read .
>>>>. . performance performance . performance performance .
>>>>. . (0.5K, MB/s) (0.5K, MB/s) . (1 MB >MB/s) (1 MB, MB/s) .
>>>>.............................................................................................
>>>>. Ethernet (1 Gb/s network) . 77 78 . 77 89 .
>>>>. IPoIB (8 Gb/s network) . 163 185 . 201 239 .
>>>>. iSER (8 Gb/s network) . 250 N/A . 360 N/A .
>>>>. SRP (8 Gb/s network) . N/A 421 . N/A 683 .
>>>>............................................................................................
>>>
>>>how are write speeds with SCST SRP?
>>>for some kernels and tests tgt writes at >2x the read speed.
>>>
>>>also I see much higher speeds that what you report in my DDR 4x IB tgt
>>>testing... which could be taken as inferring that tgt is scaling quite
>>>nicely on the faster fabric?
>>> ib_write_bw of 1473 MB/s
>>> ib_read_bw of 1378 MB/s
>>>
>>>iSER to 7G ramfs, x86_64, centos4.6, 2.6.22 kernels, git tgtd,
>>>initiator end booted with mem=512M, target with 8G ram
>>>
>>> direct i/o dd
>>> write/read 800/751 MB/s
>>> dd if=/dev/zero of=/dev/sdc bs=1M count=5000 oflag=direct
>>> dd of=/dev/null if=/dev/sdc bs=1M count=5000 iflag=direct
>>>
>>> buffered i/o dd
>>> write/read 1109/350 MB/s
>>> dd if=/dev/zero of=/dev/sdc bs=1M count=5000
>>> dd of=/dev/null if=/dev/sdc bs=1M count=5000
>>>
>>>buffered i/o lmdd
>>> write/read 682/438 MB/s
>>> lmdd if=internal of=/dev/sdc bs=1M count=5000
>>> lmdd of=internal if=/dev/sdc bs=1M count=5000
>
>
>>The tests I performed were read performance tests with dd and with
>>buffered I/O. For this test you obtained 350 MB/s with STGT on a DDR
>
>
> ... and 1.1GB/s writes :)
> presumably because buffer aggregation works well.
>
>
>>4x InfiniBand network, while I obtained 360 MB/s on a SDR 4x
>>InfiniBand network. I don't think that we can call this "scaling up"
>>...
>
>
> the direct i/o read speed being twice the buffered i/o speed would seem
> to imply that Linux's page cache is being slow and confused with this
> particular set of kernel + OS + OFED versions.
> I doubt that this result actually says that much about tgt really.
Buffered dd read is, actually, one of the best benchmarks if you want to
compare STGT vs SCST, because it's single threaded with one outstanding
command most of the time, i.e. it's a latency bound workload. Plus, most
of the applications reading files do exactly what dd does.
Both SCST and STGT suffer equally from possible problems on the
initiator, but SCST bears it much better, because it has much less
processing latency (e.g., because there are no extra user<->kernel
spaces switches and other related overhead).
>>Regarding write performance: the write tests were performed with a
>>real target (three disks in RAID-0, write bandwidth about 100 MB/s). I
>
>
> I'd be interested to see ramdisk writes.
>
> cheers,
> robin
> _______________________________________________
> Stgt-devel mailing list
> Stgt-devel-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
> https://lists.berlios.de/mailman/listinfo/stgt-devel
>
next prev parent reply other threads:[~2008-01-24 12:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 9:27 Performance of SCST versus STGT Bart Van Assche
2008-01-17 9:40 ` FUJITA Tomonori
2008-01-17 9:48 ` Vladislav Bolkhovitin
2008-01-17 10:05 ` FUJITA Tomonori
[not found] ` <20080117190558K.fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2008-01-17 10:34 ` Vladislav Bolkhovitin
[not found] ` <478F2F46.9040103-d+Crzxg7Rs0@public.gmane.org>
2008-01-17 12:29 ` Robin Humble
2008-01-17 13:44 ` [Scst-devel] [Stgt-devel] " Vladislav Bolkhovitin
[not found] ` <20080117122956.GA3567-Td5ZOp7sT3Xw02mFwxTg32+DJq1SqhBbsOSz5zK2v9k@public.gmane.org>
2008-01-17 14:43 ` Bart Van Assche
2008-01-17 17:45 ` Pete Wyckoff
[not found] ` <20080117174542.GC29650-pxmRpbKlMIQ@public.gmane.org>
2008-01-18 10:30 ` Bart Van Assche
2008-01-18 12:08 ` Vladislav Bolkhovitin
2008-01-20 9:36 ` Bart Van Assche
[not found] ` <e2e108260801200136g7f17b8a0g89a54cc1d73bbc34-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-21 12:07 ` Vladislav Bolkhovitin
2008-01-22 3:26 ` FUJITA Tomonori
[not found] ` <20080122122657R.fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2008-01-22 7:50 ` Bart Van Assche
2008-01-22 11:33 ` Vladislav Bolkhovitin
[not found] ` <4795D479.1080805-d+Crzxg7Rs0@public.gmane.org>
2008-01-22 11:48 ` FUJITA Tomonori
2008-01-22 12:20 ` Vladislav Bolkhovitin
2008-01-22 15:14 ` Bart Van Assche
2008-01-22 10:04 ` Bart Van Assche
2008-01-22 11:33 ` Vladislav Bolkhovitin
[not found] ` <4795D4A7.5000105-d+Crzxg7Rs0@public.gmane.org>
2008-01-22 12:32 ` Bart Van Assche
[not found] ` <e2e108260801220432l353b1d76xd2707b5e6f336aef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-22 15:23 ` Vladislav Bolkhovitin
2008-01-24 7:06 ` Robin Humble
2008-01-24 10:36 ` [Stgt-devel] " Bart Van Assche
2008-01-24 11:10 ` Vladislav Bolkhovitin
[not found] ` <4798720E.4020802-d+Crzxg7Rs0@public.gmane.org>
2008-01-24 11:40 ` Robin Humble
[not found] ` <20080124114027.GC26751-Td5ZOp7sT3Xw02mFwxTg32+DJq1SqhBbsOSz5zK2v9k@public.gmane.org>
2008-01-24 12:41 ` Vladislav Bolkhovitin
[not found] ` <e2e108260801240236o2273be0bw24a2a61dcc781222-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-24 11:32 ` Robin Humble
[not found] ` <20080124113215.GB26751-Td5ZOp7sT3Xw02mFwxTg32+DJq1SqhBbsOSz5zK2v9k@public.gmane.org>
2008-01-24 12:40 ` Vladislav Bolkhovitin [this message]
2008-01-24 16:16 ` [Stgt-devel] " Bart Van Assche
2008-01-24 19:54 ` Vladislav Bolkhovitin
2008-01-25 7:24 ` Bart Van Assche
2008-01-22 12:33 ` Bart Van Assche
2008-01-17 14:22 ` Erez Zilber
[not found] ` <478F64A0.6020201-hKgKHo2Ms0F+cjeuK/JdrQ@public.gmane.org>
2008-01-17 14:32 ` Vladislav Bolkhovitin
[not found] ` <478F6708.30604-d+Crzxg7Rs0@public.gmane.org>
2008-01-17 14:46 ` Erez Zilber
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=47988738.5090000@vlnb.net \
--to=vst-d+crzxg7rs0@public.gmane.org \
--cc=James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=fujita.tomonori-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robin.humble+stgt-FCV4sgi5zeUQrrorzV6ljw@public.gmane.org \
--cc=scst-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=stgt-devel-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
/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.