From: Rick Jones <rick.jones2@hp.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Sridhar Samudrala <sri@us.ibm.com>,
Tom Lendacky <toml@us.ibm.com>, netdev <netdev@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] vhost: Make it more scalable by creating a vhost thread per device.
Date: Mon, 12 Apr 2010 10:50:43 -0700 [thread overview]
Message-ID: <4BC35D73.8080801@hp.com> (raw)
In-Reply-To: <20100412174259.GA18507@redhat.com>
>>>
>>>Consider using Ingo's perf tool to get error bars, but looks good
>>>overall.
>>
>>What do you mean by getting error bars?
>
>
> How noisy are the numbers?
> I'd like to see something along the lines of 85% +- 2%
In netperf terms that would be adding the confidence intervals calculations to
the results - which will be done by that "runemomniagg2.sh" script I mentioned.
When running multiple instance tests, it is very important to set the min and
max iterations to the same value so no instance thinks to finish early. The
script does that, just want to make sure that those leveraging it do the same.
happy benchmarking,
rick jones
next prev parent reply other threads:[~2010-04-12 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 17:31 [PATCH] vhost: Make it more scalable by creating a vhost thread per device Sridhar Samudrala
2010-04-04 11:14 ` Michael S. Tsirkin
2010-04-05 17:35 ` Sridhar Samudrala
2010-04-06 18:49 ` Avi Kivity
2010-04-09 0:05 ` Sridhar Samudrala
2010-04-09 0:14 ` Rick Jones
2010-04-09 15:39 ` Sridhar Samudrala
2010-04-09 17:13 ` Rick Jones
2010-04-11 15:47 ` Michael S. Tsirkin
2010-04-12 17:35 ` Sridhar Samudrala
2010-04-12 17:42 ` Michael S. Tsirkin
2010-04-12 17:50 ` Rick Jones [this message]
2010-04-12 16:27 ` 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=4BC35D73.8080801@hp.com \
--to=rick.jones2@hp.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
--cc=toml@us.ibm.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).