From: Stefan Baranoff <sbaranoff@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] VMWare Performance - vmxnet3-usermap
Date: Fri, 18 Jul 2014 09:26:59 -0400 [thread overview]
Message-ID: <CAHzKxpbgK6zZR814jYduk2VZ0FBxZvchBoQABnWNtLkTRmaAwg@mail.gmail.com> (raw)
All,
I've been playing with DPDK recently on a variety of bare metal Linux
installations and so far and have seen wonderful improvements in
performance on both our Westmere and Sandy Bridge based servers.
However when I install ESXi 5.1 (not linked to a vSphere management system
-- stand alone ESXi installation) on one of the Westmere systems and use
vmxnet3-usermap with the standard VMWare vSwitch my performance drops way
down.
Does anyone have a sense of pps/bps I can realistically expect to see from
vmxnet3-usermap without doing SR-IOV/passthrough? Raw CentOS and RHEL 6.4
we're seeing 14.88Mpps/10Gbps but going to ESXi running CentOS 6.4 we're
seeing 500Kpps/4Gbps. Is that reasonable (obviously packet rate is with
small packets and data rate is with larger packets). Without going to
SR-IOV is there anything that I can do to improve this performance in
vmware?
Also, I know SR-IOV breaks many of the HA/auto balancing features of
VMware. Is the same true with vmxnet3-usermap or is that safe to use with
VMs floating around a cluster willy-nilly?
Thanks,
Stefan
reply other threads:[~2014-07-18 13:26 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=CAHzKxpbgK6zZR814jYduk2VZ0FBxZvchBoQABnWNtLkTRmaAwg@mail.gmail.com \
--to=sbaranoff@gmail.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).