From: "Jun Xiao" <jun.xiao@cloudnetengine.com>
To: "dev" <dev@openvswitch.org>, "discuss" <discuss@openvswitch.org>,
"dev" <dev@dpdk.org>
Subject: [dpdk-dev] More performance comparisons on virtual switches
Date: Sun, 16 Aug 2015 00:11:59 +0800 [thread overview]
Message-ID: <----Tc------lRRzc$c24dd4bf-575a-458c-85ce-f90eead6da5b@cloudnetengine.com> (raw)
Hi All,
Since we announced CloudNetEngine virtual switch technical preview, we received quite a few very good suggestions/feedbacks from evaluation customers, thank you all!
Today we release CloudNetEngine vSwitch technical preview update 1, which includes a number of performance improvements over last few weeks. Here we also share more performance comparisons on Native kernel OVS, OVS-DPDK, and CNE vSwitch technical preview update 1. The methodology for the comparison is also commonly used by virtualization vendors, i.e. end to end TCP throughput/CPU usage, and TCP_RR transaction throughput.
A few key observations:
- OVS-DPDK is not designed to optimize for intra VMs communication, its tcp throughput is even worse than Native kernel OVS.
- OVS-DPDK only wins at TCP_RR, and this is reasonable as it always keep a CPU core 100% busy.
- CNE vSwitch wins on almost all metrics (except OVS_DPDK's TCP_RR), and its TCP throughput/CPU efficiency is around 3X against Native kernel OVS while also provides better TCP_RR throughput than Native kernel OVS.
For more information, please refer to http://cloudnetengine.com/en/blog/2015/08/15/more/
If you want to try CNE vSwitch technical preview update 1, please don't hesitate to send a evaluation request to info@cloudnetengine.com.
Thanks,Jun Xiaowww.cloudnetengine.com
reply other threads:[~2015-08-15 16:12 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='----Tc------lRRzc$c24dd4bf-575a-458c-85ce-f90eead6da5b@cloudnetengine.com' \
--to=jun.xiao@cloudnetengine.com \
--cc=dev@dpdk.org \
--cc=dev@openvswitch.org \
--cc=discuss@openvswitch.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).