From: Bart Van Assche <bart.vanassche@gmail.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Vladislav Bolkhovitin <vst@vlnb.net>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
iscsitarget-devel@lists.sourceforge.net,
James Bottomley <James.Bottomley@hansenpartnership.com>,
scst-devel <scst-devel@lists.sourceforge.net>,
stgt@vger.kernel.org
Subject: Re: [Scst-devel] [ANNOUNCE]: Comparison of features sets between different SCSI targets (SCST, STGT, IET, LIO)
Date: Tue, 7 Apr 2009 22:27:36 +0200 [thread overview]
Message-ID: <e2e108260904071327u6b6c6e43tdc76f648be0302dd@mail.gmail.com> (raw)
In-Reply-To: <49DA49AA.1060106@wpkg.org>
On Mon, Apr 6, 2009 at 8:27 PM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
> Note that crypt performance for SCST was worse than that of STGT for large
> read-ahead values.
> Also, SCST performance on crypt device was more or less the same with 256
> and 16384 readahead values. I wonder why performance didn't increase here
> while increasing readahead values? Could anyone recheck if it's the same on
> some other system?
I have repeated the test for the non-encrypted case. Setup details:
* target: 2.6.29.1 kernel, 64-bit, Intel E8400 CPU @ 3 GHz, 4 GB RAM,
two ST3250410AS disks, with /dev/md3 set up in RAID-1 with a stripe
size of 32 KB, local reading speed of /dev/md3: 120 MB/s, I/O
scheduler: CFQ.
* initiator: 2.6.28.7 kernel, 64-bit, Intel E6750 CPU @ 2.66 GHz, 2 GB RAM.
* network: 1 Gbit/s Ethernet, two systems connected back to back via a
crossed cable.
Each test was repeated four times. Before each test the target caches
were dropped via the command "sync; echo 3 >
/proc/sys/vm/drop_caches". The following test has been run on the
initiator:
sync; echo 3 > /proc/sys/vm/drop_caches; dd if=/dev/sdb of=/dev/null
bs=64K count=100000
Results with read-ahead set to 256 on the initiator, in MB/s:
STGT 56.7 +/- 0.3
SCST 56.9 +/- 1.1
Results with read-ahead set to 16384 on the initiator, in MB/s:
STGT 59.9 +/- 0.1
SCST 59.5 +/- 0.0
Or: slightly better results with the larger read-ahead value, and a
performance difference well below 1% between the STGT and SCST
performance results.
Bart.
next prev parent reply other threads:[~2009-04-07 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 18:56 Vladislav Bolkhovitin
2009-04-04 19:12 ` [Scst-devel] " Tomasz Chmielewski
2009-04-04 19:21 ` Vladislav Bolkhovitin
2009-04-06 9:44 ` Tomasz Chmielewski
2009-04-05 11:29 ` Bart Van Assche
2009-04-06 10:29 ` Tomasz Chmielewski
2009-04-06 10:40 ` Tomasz Chmielewski
2009-04-06 16:55 ` Vladislav Bolkhovitin
2009-04-06 18:27 ` Tomasz Chmielewski
2009-04-07 20:27 ` Bart Van Assche [this message]
2009-04-09 18:45 ` Vladislav Bolkhovitin
2009-04-14 11:07 ` Tomasz Chmielewski
2009-04-14 18:10 ` Vladislav Bolkhovitin
2009-04-06 19:01 ` Bart Van Assche
2009-04-06 19:05 ` Tomasz Chmielewski
[not found] ` <c9a3e4540904052019o3c89128eq52d9046fef7e2725@mail.gmail.com>
2009-04-06 7:32 ` Vladislav Bolkhovitin
[not found] ` <c9a3e4540904060057w75b5525an9c63486ed00ca9a5@mail.gmail.com>
2009-04-06 12:21 ` Vladislav Bolkhovitin
[not found] ` <c9a3e4540904060319l3c885641k1217fba468f1fcf8@mail.gmail.com>
2009-04-06 17:57 ` 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=e2e108260904071327u6b6c6e43tdc76f648be0302dd@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=iscsitarget-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=scst-devel@lists.sourceforge.net \
--cc=stgt@vger.kernel.org \
--cc=vst@vlnb.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
all inboxes | Powered by JetHome®