From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: James Dykman <dykman-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: PV network performance comparison
Date: Mon, 15 Oct 2007 10:51:13 +0200 [thread overview]
Message-ID: <47132A01.2000605@qumranet.com> (raw)
In-Reply-To: <OF0BAE27C6.6B75A1D6-ON85257371.00749F3B-85257371.007646DD-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
James Dykman wrote:
> Dor,
>
> I ran some netperf tests with your PV
> virtio drivers, along with some Xen PV cases
> and a few others for comparison. I thought you
> (and the list) might be interested in the numbers.
>
> I am going to start looking for bottlenecks, unless
> you need help with the new hypercall updates.
> I'll re-run when that is available.
>
> Jim
>
> TCP REQUEST/RESPONSE (Trans. Rate per sec)
> size kvm.rtl kvm.pv xen.pv xen.um kvm.lo
> 1 2191.47 9533.74 18052.37 13593.58 42400.73
> 64 2184.30 9518.13 17979.93 13557.98 42260.53
> 128 2177.52 9482.45 17940.08 13588.54 40983.90
> 256 2160.49 9465.97 17788.21 13492.42 41170.45
> 512 2130.99 9403.33 17655.11 13489.64 40765.26
> 1024 2074.85 9204.90 17293.06 13572.01 39437.78
> 2048 416.18 4750.41 12907.57 11571.07 37252.42
> 4096 265.22 3691.90 10990.67 9943.64 31905.03
> 8192 116.80 1892.25 8439.83 6604.64 24397.95
> 16384 92.06 1004.58 4535.86 3924.68 17460.30
>
>
A flood ping from guest to host gives almost 10000 transmissions/sec
with the rtl8139 with an FC6 x86_64 guest here.
> TCP STREAM (Throughput 10^6bits/sec)
> size kvm.rtl kvm.pv xen.pv xen.um kvm.lo
> 2048 33.06 507.21 555.94 1442.38 5409.73
> 4096 33.16 526.75 848.26 2359.42 6152.48
> 8192 33.13 527.99 997.69 2418.87 7267.73
> 16384 33.08 525.95 1107.64 2379.50 8434.29
> 32768 33.13 525.38 1199.08 2375.81 8857.09
> 65536 33.20 523.39 1255.33 2473.92 9248.35
> 131072 33.11 520.87 1292.54 2605.49 8559.21
>
xen.um is higher than xen.pv?
I get 8.4 MB/s (67Mb/s) using netcat from guest to host.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-15 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 21:30 PV network performance comparison James Dykman
[not found] ` <OF0BAE27C6.6B75A1D6-ON85257371.00749F3B-85257371.007646DD-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-10-11 23:12 ` Dor Laor
2007-10-15 5:34 ` Zhao Forrest
[not found] ` <ac8af0be0710142234q19155a7aia00adf12d0c6e62a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-15 8:58 ` Avi Kivity
2007-10-15 8:51 ` Avi Kivity [this message]
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=47132A01.2000605@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=dykman-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.