From: zimeiw <zimeiw@163.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: dpdk native tcp/ip stack (ans) performance reach 11.78Mpps
Date: Fri, 8 Dec 2017 08:41:43 +0800 (CST) [thread overview]
Message-ID: <21a1a055.eda.16033922313.Coremail.zimeiw@163.com> (raw)
hi,
Share dpdk tcp/ip stack performance here:
CPU
Intel(R) Xeon(R) CPU E5-2683 v3 @ 2.00GHz
NIC
02:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
02:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)
| routing forwarding performance |
| (one lcore) |
|--------------------------------------|
| Packet size(byte)| Throughput(Mpps) |
|--------------------------------------|
| 64 | 11.78 |
|--------------------------------------|
| 128 | Line Rate |
|--------------------------------------|
If add 1000 route entity, the performance isn't reduced.
The performance increases as core increases.
For detail steps, please refer to doc(https://github.com/ansyun/dpdk-ans/blob/master/doc/guides/ans_performance_report.pdf)
--
Best Regards,
ANS-DEV-TEAM
reply other threads:[~2017-12-08 0:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=21a1a055.eda.16033922313.Coremail.zimeiw@163.com \
--to=zimeiw@163.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).