From: "Gray, Mark D" <mark.d.gray@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Jun Xiao <jun.xiao@cloudnetengine.com>
Cc: dev <dev@dpdk.org>, discuss <discuss@openvswitch.org>
Subject: Re: [dpdk-dev] vswitches performance comparison
Date: Wed, 22 Jul 2015 08:07:04 +0000 [thread overview]
Message-ID: <738D45BC1F695740A983F43CFE1B7EA92E2BF8DF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20150721140205.485d35b4@urahara>
> "Jun Xiao" <jun.xiao@cloudnetengine.com> wrote:
>
> > After CloudNetEngine vswitch technical preview is launched, we
> > received quite a few queries on vswitches performance comparison, but
> > we cannot simply give a test result on our platform because
> > performance varies on different H/Ws and different workloads, and
> > that's why we encourage you to try the evaluation package to get real data
> on your setup.
> >
> > Anyway, we share a little more performance data on our H/W which is a
> > comparison among native kernel OVS/OVS-DPDK/CNE vswitch under the
> most common workload:
> > concurrent bi-directional TCP traffics cross hosts, and hope you can have a
> rough idea.
> > http://www.cloudnetengine.com/weblog/2015/07/22/vswitches-
> performance-
> > comparison/
> >
> > Thanks,
> > Jun
>
> Since the real bottleneck in most vswitches is per-packet overhead.
> I would recommend running RFC-2544 tests for better data.
>
> You probably need to use something like pktgen to get enough packets-per-
> second.
Yeah this is the methodology that we use aswell.
prev parent reply other threads:[~2015-07-22 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 18:00 Jun Xiao
2015-07-21 18:14 ` [dpdk-dev] [ovs-discuss] " Gray, Mark D
2015-07-21 18:28 ` Jun Xiao
2015-07-21 18:36 ` Gray, Mark D
2015-07-21 18:48 ` Jun Xiao
2015-07-22 8:06 ` Gray, Mark D
2015-07-21 21:02 ` [dpdk-dev] " Stephen Hemminger
2015-07-22 8:07 ` Gray, Mark D [this message]
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=738D45BC1F695740A983F43CFE1B7EA92E2BF8DF@IRSMSX108.ger.corp.intel.com \
--to=mark.d.gray@intel.com \
--cc=dev@dpdk.org \
--cc=discuss@openvswitch.org \
--cc=jun.xiao@cloudnetengine.com \
--cc=stephen@networkplumber.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).