From: Luca Bigliardi <shammash@artha.org>
To: kvm@vger.kernel.org
Subject: kvm network latency, higher with virtio ?
Date: Tue, 15 Sep 2009 17:15:09 +0200 [thread overview]
Message-ID: <20090915151509.GC22518@esaurito.net> (raw)
Hi,
I'm running some tests between two linux instances bridged together.
If I try to ping 10 times I obtain the following results:
-net nic,model=virtio -net tap :
rtt min/avg/max/mdev = 0.756/0.967/2.115/0.389 ms
-net nic,model=rtl8139 -net tap :
rtt min/avg/max/mdev = 0.301/0.449/1.173/0.248 ms
So it seems with virtio the latency is higher. Is it normal?
The results I'm reporting were obtained with
- host
qemu-kvm 0.11-rc2
kvm-kmod-2.6.30.1
kernel: 2.6.30.5 (HIGH_RES_TIMERS=y as suggested in
http://www.linux-kvm.org/page/Virtio )
- guest
kernel: 2.6.31
but I also tested older versions always obtaining latency values at least two
times higher than rtl8139/e1000 .
Thank you,
Luca
next reply other threads:[~2009-09-15 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 15:15 Luca Bigliardi [this message]
2009-09-16 7:27 ` kvm network latency, higher with virtio ? Michael S. Tsirkin
2009-09-16 8:47 ` Dor Laor
2009-09-17 16:58 ` Luca Bigliardi
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=20090915151509.GC22518@esaurito.net \
--to=shammash@artha.org \
--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;
as well as URLs for NNTP newsgroup(s).