From: Rick Jones <rick.jones2@hp.com>
To: Qin Chuanyu <qinchuanyu@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: jasowang@redhat.com, Anthony Liguori <anthony@codemonkey.ws>,
KVM list <kvm@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: 8% performance improved by change tap interact with kernel stack
Date: Tue, 28 Jan 2014 08:56:34 -0800 [thread overview]
Message-ID: <52E7E142.8000407@hp.com> (raw)
In-Reply-To: <52E77506.1080604@huawei.com>
On 01/28/2014 01:14 AM, Qin Chuanyu wrote:
> On 2014/1/28 16:34, Michael S. Tsirkin wrote:
>> Could you please check latency results?
>>
> netperf UDP_RR 512
> test model: VM->host->host
>
> modified before : 11108
> modified after : 11480
>
> 3% gained by this patch
Netperf UDP_RR can be very sensitive to packet losses. Not that there
were necessarily any in your tests, but to further confirm the 3%
improvement in latency, I would suggest using the confidence intervals
functionality in your before/after netperf testing. And to get at what
Michael asks about CPU utilization I would suggest:
netperf -H <otherguy> -c -C -l 30 -i 30,3 -t UDP_RR -- -r 512
(I was guessing as to what netperf options you may have been using already)
happy benchmarking,
rick jones
next prev parent reply other threads:[~2014-01-28 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 8:14 8% performance improved by change tap interact with kernel stack Qin Chuanyu
2014-01-28 8:34 ` Michael S. Tsirkin
2014-01-28 9:14 ` Qin Chuanyu
2014-01-28 9:41 ` Michael S. Tsirkin
2014-01-28 10:19 ` Qin Chuanyu
2014-01-28 10:33 ` Michael S. Tsirkin
2014-01-28 16:58 ` Stephen Hemminger
2014-01-28 17:18 ` Michael S. Tsirkin
2014-01-29 7:41 ` Qin Chuanyu
2014-01-29 7:56 ` Michael S. Tsirkin
2014-01-28 16:56 ` Rick Jones [this message]
2014-01-28 14:49 ` Eric Dumazet
2014-01-29 7:12 ` Qin Chuanyu
2014-02-11 13:21 ` Qin Chuanyu
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=52E7E142.8000407@hp.com \
--to=rick.jones2@hp.com \
--cc=anthony@codemonkey.ws \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qinchuanyu@huawei.com \
/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).