From: Dario Faggioli <dario.faggioli@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Call to write tests for osstest
Date: Fri, 9 Aug 2013 14:16:34 +0200 [thread overview]
Message-ID: <1376050594.2891.17.camel@Abyss> (raw)
In-Reply-To: <998004135.20130809140441@eikelenboom.it>
[-- Attachment #1.1: Type: text/plain, Size: 1408 bytes --]
On ven, 2013-08-09 at 14:04 +0200, Sander Eikelenboom wrote:
> Friday, August 9, 2013, 2:00:08 PM, you wrote:
> > This worries me. It is really hard to keep the "environment" the same.
> > AIUI network / block etc. performance can be affected by other kernel
> > subsystems. Also the kernel config could also have impact on
> > performance.
>
> True, though you probably should be able to make out a general trend when putting it in graphs.
> And add a milestone when you significantly alter the config of a machine.
>
Indeed.
However let's not run too fast. The final goal is the one you stated in
you're first e-mail. The first step is make it possible to run
performance benchmarks on top of OSSTest.
That way, even before adding these kind of tests to automated testing,
people could use that to investigate the performance impact of some
change they're working on.
Let's figure out the details on whether and how to merge it with the
push gate machinery after we have the mechanism itself in place, ok? :-)
Sander, I can keep you posted on progresses I make, if you're interested
in that.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-09 12:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 16:01 Call to write tests for osstest George Dunlap
2013-08-08 17:32 ` Sander Eikelenboom
2013-08-08 19:42 ` Konrad Rzeszutek Wilk
2013-08-09 11:19 ` Dario Faggioli
2013-08-09 11:46 ` Sander Eikelenboom
2013-08-09 12:00 ` Wei Liu
2013-08-09 12:04 ` Sander Eikelenboom
2013-08-09 12:16 ` Dario Faggioli [this message]
2013-08-14 15:03 ` George Dunlap
2013-08-08 17:37 ` Sander Eikelenboom
2013-08-14 13:51 ` George Dunlap
2013-08-08 19:40 ` Konrad Rzeszutek Wilk
2013-08-14 13:52 ` George Dunlap
2013-08-13 14:24 ` Ben Guthro
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=1376050594.2891.17.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).