linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Cliff White <cliffw@osdl.org>
Cc: linux-mm@kvack.org
Subject: Re: Automated performance testing system was Re: Text form for STP tests
Date: Wed, 1 Dec 2004 11:16:07 -0200	[thread overview]
Message-ID: <20041201131607.GH2250@dmt.cyclades> (raw)
In-Reply-To: <200412011828.iB1ISOr04501@mail.osdl.org>

On Wed, Dec 01, 2004 at 10:28:24AM -0800, Cliff White wrote:
> > Linux-MM fellows,
> > 
> > I've been talking to Cliff about the need for a set of benchmarks,
> > covering as many different workloads as possible, for developers to have a 
> > better notion of impact on performance changes. 
> > 
> > Usually when one does a change which affects performance, he/she runs one 
> > or two benchmarks with a limited amount of hardware configurations.
> > This is a very painful, boring and time consuming process, which can 
> > result in misinterpretation and/or limited understading of the results 
> > of such changes.
> > 
> > It is important to automate such process, with a set of benchmarks 
> > covering as wide as possible range of workloads, running on common 
> > and most used hardware variations.
> > 
> > OSDL's STP provides the base framework for this.
> > 
> [ snip ]
> > bonnie++
> > reaim (default, new_fserver, shared)
> > dbench_long
> > kernbench
> > tiobench
> > 
> > Each of these running one the following combinations:
> > 
> > 1CPU, 2CPU, 4CPU, 8CPU (4 variants).
> > 
> > total memory, half memory, a quarter of total memory (3 variants).
> > 
> > Thats 12 results for each benchmark."
> > 
> The configuration files to do these tests are now written, and the humble
> robots are running this test series against linux-2.6.7 ( for history data )
> There will need to be some adjustments - some of these tests will no doubt
> fail for reasons of script error or configuration ( i see already kernbench will 
> have to be redunced for 1-cpu systems, as it runs > 13.5 hours :( )
> 
> And, the second part of the automation is already done, but needs input.
> I can aim this test battery at any kernel patch, where 'any kernel patch'
> is identified by a regexp. What kernels do you want this against? 

The most recent 2.6.10-rc2 and 2.6.10-rc2-mm in STP.

Will this be available through the web interface? 

Thanks again Cliff

> I've heard mention of 'baseline' - we call this baseline:
> 
> /^(patch|linux)-\d+\.\d+\.\d+$/
> 
> ( starts with 'patch' or 'linux', then '-' followed by three decimals ) 
> 
> cliffw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-12-01 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041125093135.GA15650@logos.cnet>
     [not found] ` <200411282017.iASKH2F05015@mail.osdl.org>
2004-11-30  0:42   ` Marcelo Tosatti
2004-11-30 17:00     ` Martin J. Bligh
2004-11-30 17:11       ` cliff white
2004-12-01 18:28     ` Cliff White
2004-12-01 13:16       ` Marcelo Tosatti [this message]
2004-12-01 20:04         ` Cliff White
2004-12-13 11:42           ` Marcelo Tosatti
2004-12-13 16:22             ` cliff white
2004-12-13 21:02               ` Marcelo Tosatti
2004-12-14 18:11                 ` Cliff White

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=20041201131607.GH2250@dmt.cyclades \
    --to=marcelo.tosatti@cyclades.com \
    --cc=cliffw@osdl.org \
    --cc=linux-mm@kvack.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