From: Gregory Haskins <gregory.haskins@gmail.com>
To: alacrityvm-devel@lists.sourceforge.net,
alacrityvm-users@lists.sourceforge.net
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org
Subject: AlacrityVM numbers updated for 31-rc4
Date: Wed, 12 Aug 2009 16:43:23 -0400 [thread overview]
Message-ID: <4A83296B.3080606@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
I re-ran the numbers on 10GE against the actual alacrityvm v0.1 release
available in git on kernel.org.
I tried to include the newly announced "vhost" driver (Michael Tsirkin)
for virtio acceleration, but ran into issues getting the patches to apply.
For now, this includes native, virtio-u (virtio-userspace), and venet
all running on 31-rc4. If I can resolve the issue with Michaels
patches, I will add "virtio-k" (virtio-kernel) to the mix as well. For
now, here are the results for 1500mtu:
native: 7388Mb/s, 29.8us rtt (33505 tps udp-rr)
venet: 3654Mb/s, 56.8us rtt (17600 tps udp-rr)
virtio-u: 1955Mb/s, 4016.0us rtt ( 249 tps udp-rr)
Note that on one particular boot-session, I actually saw venet run
consistently 4600Mb/s, and virtio-u run consistently 2800Mb/s. I am not
sure why other runs resulted in deterministically lower numbers, but I
included the average of the low runs to be conservative, ~3600, ~1900
respectively).
Of interest here is that native made a huge jump (2.6.29 was more like
4Gb/s), and also that KVM regressed a bit, especially compared to native
numbers. The cause for either of these changes is not known at this
time, but I will investigate the cause over the next few days.
In any case, I have updated the graphs on the AlacrityVM wiki to reflect
these latest numbers:
http://developer.novell.com/wiki/index.php/AlacrityVM
Kind Regards,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next reply other threads:[~2009-08-12 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 20:43 Gregory Haskins [this message]
2009-08-12 21:33 ` AlacrityVM numbers updated for 31-rc4 Javier Guerra
2009-08-12 22:05 ` Michael S. Zick
2009-08-12 23:05 ` Anthony Liguori
2009-08-12 23:21 ` Gregory Haskins
2009-08-13 12:05 ` Gregory Haskins
2009-08-14 19:50 ` Gregory Haskins
2009-08-17 11:06 ` Michael S. Tsirkin
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=4A83296B.3080606@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=alacrityvm-devel@lists.sourceforge.net \
--cc=alacrityvm-users@lists.sourceforge.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.