From: Cliff White <cliffw@osdl.org>
To: Mark Peloquin <peloquin@austin.ibm.com>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Nightly regression runs against current bk tree
Date: Thu, 29 May 2003 16:30:48 -0700 [thread overview]
Message-ID: <200305292330.h4TNUmd30434@mail.osdl.org> (raw)
In-Reply-To: Message from Andreas Dilger <adilger@clusterfs.com> of "Thu, 29 May 2003 17:17:03 MDT." <20030529171703.U29153@schatzie.adilger.int>
> On May 29, 2003 17:48 -0500, Mark Peloquin wrote:
> > Your correct. We're just getting started with this effort and we used
> > this mix to get things going. Once ppl are happy with the presentation
> > of data, we planned to add more tests to provide a more balanced mix.
> > But since you asked, we have added lmbench to our -bk3 regression run. :)
>
> Mark, it would be nice to get a graph of the combined results for each
> test. Something like:
>
> tiobench sequential write rate
> | +++++++++++++++++ + = -mm-ext3
> M | ++++++++++++++++++++++++++***************** * = linus-ext3
> B | +++++++***************** ###### # = -ac-ext3
> / | . = -mm-XFS
> s | = = -ac-XFS
> | ********* etc
> |
> +----------------------------------------------------
> date
>
> This allows at-a-glance trends for each group of tests and (as in the
> example above you could see easily when a performance bug was added
> and fixed in -ac before in the linus kernel, for example). Probably
> having all of the comparable results on the same page, or even in the
> same graph results is a win.
>
> Bonus points if you can click on a spot in the graph and get the results
> page for that date/test ;-).
This idea the STP team really, really likes. We'll start working on getting
this type of report
into our framework.
Thanks much, Andreas - great explaination.
cliffw
>
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-05-29 23:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3ED66C83.8070608@austin.ibm.com.suse.lists.linux.kernel>
2003-05-29 21:11 ` Andi Kleen
2003-05-29 21:25 ` David S. Miller
2003-05-29 21:29 ` Andi Kleen
2003-05-29 21:38 ` Randy.Dunlap
2003-05-29 21:48 ` David S. Miller
2003-05-29 22:04 ` Craig Thomas
2003-05-29 22:05 ` Andi Kleen
2003-05-29 22:25 ` Cliff White
2003-05-29 23:41 ` David S. Miller
2003-05-29 21:50 ` Craig Thomas
2003-05-29 22:03 ` Andi Kleen
2003-05-29 22:16 ` Cliff White
2003-05-29 22:23 ` Nathan
2003-05-29 23:10 ` Mark Peloquin
2003-05-29 22:51 ` Mark Peloquin
2003-05-29 22:03 ` Nathan
2003-05-29 23:08 ` Mark Peloquin
2003-05-29 22:48 ` Mark Peloquin
2003-05-29 23:17 ` Andreas Dilger
2003-05-29 23:30 ` Cliff White [this message]
2003-06-03 16:04 Paul Larson
-- strict thread matches above, loose matches on Subject: below --
2003-05-29 20:24 Mark Peloquin
2002-10-27 12:13 New nanosecond stat patch for 2.5.44 Andi Kleen
2002-10-27 14:33 ` New nanosecond stat patch for 2.5.44 - new patch II Andi Kleen
2002-10-27 21:49 ` New nanosecond stat patch for 2.5.44 Andreas Dilger
2002-10-27 22:54 ` H. Peter Anvin
2002-10-28 1:23 ` Chris Friesen
2002-10-28 1:35 ` Rob Landley
2002-11-06 13:27 ` Gabriel Paubert
2002-11-06 18:00 ` H. Peter Anvin
2002-10-27 23:16 ` Horst von Brand
2002-10-28 17:10 ` Andreas Dilger
2002-10-29 15:01 ` Bill Davidsen
2002-10-29 16:30 ` Andreas Dilger
2002-10-29 20:37 ` Bill Davidsen
2002-10-30 0:44 ` Jamie Lokier
2002-10-30 21:12 ` Bill Davidsen
2002-10-30 22:17 ` Jamie Lokier
2002-10-31 0:34 ` H. Peter Anvin
2002-11-01 1:57 ` Bill Davidsen
2002-11-01 3:32 ` Jamie Lokier
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=200305292330.h4TNUmd30434@mail.osdl.org \
--to=cliffw@osdl.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peloquin@austin.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
all inboxes | Powered by JetHome®