From: Lutz Vieweg <lvml@5t9.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] macvtap performance: good when writing from guest, abysmal when reading on guest (~ 700kB/s)
Date: Fri, 20 Jan 2012 16:10:20 +0100 [thread overview]
Message-ID: <jfc04s$dju$1@dough.gmane.org> (raw)
Hi,
I've been using qemu-kvm along with ordinary tap-devices and software bridges
for quite some time. When I recently noticed that a certain TCP connection between
a guest and a remote physical host was limited to ~ 80MB/s, I thought it would
be a good idea to check whether by using "macvtap", instead, the performance
would get better.
So I setup a guest on a host that has a direct peer-to-peer 10G cable to
another host, and configured it to use a macvtap device.
Then I did some benchmarks, using "nc" on both sides, just reading from /dev/zero,
writing to /dev/null.
When the guest VM is writing into a TCP connection to the physical host (linux-3.1.6),
the performance is ~ 140MB/s - not great, but better than with ordinary
tap devices.
But to my big surprise, the performance when the physical host is writing,
and the guest VM is reading is abysmal, only ~ 700kB/s!
No bottleneck is obvious - the CPU usage and NIC utilization of both
the VM, its host, and the other host is all quite low.
"strace" on qemu process indicates that from time to time, there are "pauses" of ~ 0.5
seconds in between the many reads from /dev/tapX, but I am not sure whether
this is the whole reason for the bad performance.
Any ideas?
Or should I rather stay with ordinary tap/brctl, or try yet another
virtual NIC technique?
Regards,
Lutz Vieweg
next reply other threads:[~2012-01-20 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 15:10 Lutz Vieweg [this message]
2012-01-20 22:20 ` [Qemu-devel] macvtap performance: good when writing from guest, abysmal when reading on guest (~ 700kB/s) Lutz Vieweg
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='jfc04s$dju$1@dough.gmane.org' \
--to=lvml@5t9.de \
--cc=qemu-devel@nongnu.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).