linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Cliff White <cliffw@osdl.org>,
	linux-mm@kvack.org
Subject: Re: Automated performance testing system was Re: Text form for STP tests
Date: Tue, 30 Nov 2004 09:00:59 -0800	[thread overview]
Message-ID: <127280000.1101834058@[10.10.2.4]> (raw)
In-Reply-To: <20041130004212.GB2310@dmt.cyclades>

> 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.
> 
> Cliff mentioned an internal tool they are developing for this purpose, 
> based on XML-like configuration files. 
> 
> I have suggested him a set of benchmarks (available on STP right now, 
> we want to add other benchmarks there whenever necessary) and a set of 
> CPU/memory variations.

Sounds like a good plan in general, by why on earth would you want to do
it in XML? Personally I'm not that much into masochism. A simple text
control file is perfectly sufficient (and yes, we do this internally).

M.

--
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-11-30 17:00 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 [this message]
2004-11-30 17:11       ` cliff white
2004-12-01 18:28     ` Cliff White
2004-12-01 13:16       ` Marcelo Tosatti
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='127280000.1101834058@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=cliffw@osdl.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo.tosatti@cyclades.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