public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Peloquin <peloquin@austin.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: Nightly regression runs against current bk tree
Date: Thu, 29 May 2003 15:24:35 -0500	[thread overview]
Message-ID: <3ED66C83.8070608@austin.ibm.com> (raw)


Our team would like to assist the community in quickly identifying 
patches that provide
performance improvements or regressions in the 2.5 kernel tree. The way 
to do this
will be to run a nightly regression test suite against the current bk 
tree, and then compare
the results against the previous night's results, showing the 
differences. Additionally,
also comparing against the 2.5 point release.

We have dedicated a machine and thrown together some scripts that will grab
and build the latest kernel files, execute the regression suite, 
collecting (hopefully)
enough system state information to allow meaningful analysis of any peculiar
results encountered.

Here are links to the current regression results obtained:

2.5.70 vs 2.5.70-bk1:
http://www.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk1/2.5.70-vs-2.5.70-bk1/

2.5.70 vs 2.5.70-bk2:
http://www.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk2/2.5.70-vs-2.5.70-bk2/
2.5.70-bk1 vs 2.5.70-bk2
http://www.ibm.com/developerworks/oss/linuxperf/regression/2.5.70-bk2/2.5.70-bk1-vs-2.5.70-bk2/

The regression suite executes in about 7.5 hours currently. We would 
like to keep
the execution time below 12 hours, so when a problem is encountered, we 
will have
time to recover without falling behind on the daily snapshots. We have 
attempted
to strike a balance between test execution time and test coverage. Work 
is still
ongoing in the area to provide the best balance and maintain repeatability.

Currently the regression suite operates on the 2.5 kernel bk tree. We do 
plan on
adding another machine that will perform similiar regression comparisons 
for the
-mm and -mjb patches.

Please bear in mind this is work in progress and there might be a few 
rough edges.
However, with your input, we feel it can provide a useful function. 
Please do not
hesitate to provide feedback or suggestions on improvements including 
content
and presentation.

Mark Peloquin
IBM Linux performance team


             reply	other threads:[~2003-05-29 20:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 20:24 Mark Peloquin [this message]
     [not found] <3ED66C83.8070608@austin.ibm.com.suse.lists.linux.kernel>
2003-05-29 21:11 ` Nightly regression runs against current bk tree 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
  -- strict thread matches above, loose matches on Subject: below --
2003-06-03 16:04 Paul Larson

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=3ED66C83.8070608@austin.ibm.com \
    --to=peloquin@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.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