From: David Mohr <damailings@mcbf.net>
To: <kvm@vger.kernel.org>
Subject: Networking latency - what to expect?
Date: Tue, 27 Nov 2012 16:26:21 -0700 [thread overview]
Message-ID: <65e3a10030795eacd577b0fac1a10bb1@de.mcbf.net> (raw)
Hi,
we were investigating some performance issue that an application on our
kvm VMs had and noticed that network latency is much worse in a VM
compared to actual hardware.
Initially we were using virtio network cards, but not vhost-net. After
enabling vhost the performance improved quite a bit, but is still only
at around 50% of what the actual hardware can do.
The question is, what can we expect? CPU utilization was never higher
than 50% kvm and 20% vhost. Other details are below, please let me know
if you can recommend other tests or important details that I could
provide.
I ran the following tests using netperf -t UDP_RR (all results are
transactions/sec):
* host->host 19k
* vm->its host 17k
* vm->vm (same host) 22k
* vm->vm (diff. hosts) 7k
Host: Debian squeeze using a 3.5.2 kernel
KVM: 1.1.2 (bpo)
Host CPU: Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz
VM: Debian squeeze using a 3.2.20 kernel
Network: e1000 & gigabit switch
Command-line:
-cpu host -name testvm -m 12288 -smp 16 -pidfile
/var/run/ganeti/kvm-hypervisor/pid/testvm -balloon virtio -daemonize
-monitor
unix:/var/run/ganeti/kvm-hypervisor/ctrl/testvm.monitor,server,nowait
-serial
unix:/var/run/ganeti/kvm-hypervisor/ctrl/testvm.serial,server,nowait
-usbdevice tablet -vnc 127.0.0.1:5102 -netdev
type=tap,id=netdev0,fd=8,vhost=on -device
virtio-net-pci,mac=52:54:00:00:01:e6,netdev=netdev0 -netdev
type=tap,id=netdev1,fd=9,vhost=on -device
virtio-net-pci,mac=52:54:00:00:01:e7,netdev=netdev1 -qmp
unix:/var/run/ganeti/kvm-hypervisor/ctrl/testvm.qmp,server,nowait -S
Thanks,
~David
next reply other threads:[~2012-11-27 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 23:26 David Mohr [this message]
2012-11-29 14:48 ` Networking latency - what to expect? Julian Stecklina
2012-11-29 15:50 ` David Mohr
2012-11-29 16:35 ` Julian Stecklina
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=65e3a10030795eacd577b0fac1a10bb1@de.mcbf.net \
--to=damailings@mcbf.net \
--cc=kvm@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