From: "Liu, Changcheng" <changcheng.liu@intel.com>
To: linux-rdma@vger.kernel.org
Subject: rdma performance verification
Date: Mon, 16 Sep 2019 17:42:34 +0800 [thread overview]
Message-ID: <20190916094234.GA11772@jerryopenix> (raw)
Hi all,
I'm working on using rdma to improve message transaction performance
on distributed storage system(Ceph) development.
Does anyone know what's the right tool to compare RDMA vs TCP peformance?
Such as bandwidth, latency. Especially the tool that could measure
the time to transact the same data size.
Previously, I use iperf & ib_send_bw to do test(send same data size).
However, it shows that ib_send_bw use more time to send data than
iperf.
nstcc1@nstcloudcc1:~$ time ib_send_bw -c RC -d rocep4s0 -i 1 -p 18515 -q 1 -r 4096 -t 1024 -s 1073741824 --report_gbits -F 192.168.199.222
real 3m53.858s
user 3m48.456s
sys 0m5.318s
nstcc1@nstcloudcc1:~$ time iperf -c 192.168.199.222 -p 8976 -n 1073741824 -P 1
real 0m1.688s
user 0m0.020s
sys 0m1.644s
In Ceph, the result shows that rdma performance (RC transaction type,
SEDN operation) is worse or not much better than TCP implemented performance.
Test A:
1 client thread send 20GB data to 1 server thread (marked as 1C:1S)
Result:
1) implementation based on RDMA
Take 171.921294s to finish send 20GB data.
2) implementation based on TCP
Take 62.444163s to finish send 20GB data.
Test B:
16 client threads send 16x20GB data to 1 server thread (marked as 16C:1S)
Result:
1) implementation base on RDMA
Take 261.285612s to finish send 16x20GB data.
2) implementation based on TCP
Take 318.949126 to finish send 16x20GB data.
B.R.
Changcheng
next reply other threads:[~2019-09-16 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 9:42 Liu, Changcheng [this message]
2019-10-21 20:30 ` rdma performance verification Doug Ledford
2019-10-22 12:05 ` Liu, Changcheng
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=20190916094234.GA11772@jerryopenix \
--to=changcheng.liu@intel.com \
--cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox