mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernd Eckenfels <ecki-news2002-08@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] VM Regress - A VM regression and test tool
Date: Mon, 12 Aug 2002 03:40:26 +0200	[thread overview]
Message-ID: <E17e4C2-0005yH-00@sites.inka.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0208112109110.16360-100000@skynet>

In article <Pine.LNX.4.44.0208112109110.16360-100000@skynet> you wrote:
> It works by using kernel modules to get a definite view of what the kernel
> is at and to provide reliable, reproducible tests. Modules are divided
> up into 4 catagories. Core modules provide infrastructure for the tool.
> Sense modules tell what is going on in the VM. Test tests particular
> features and bench modules (none yet) will benchmark different sections
> of the VM.

This sounds more like a micro benchmark tool, which is a good start, but the
real problem with VM optimizations is, that they have to take into account
real world load and especially user experience.

A simple example is the fact, that an idle desktop box will feel very sluggy
if a user comes back after a few hours break, because all visible programs
are paged out. To improve this, one could think about adding a flag to
applications like "connected to gui". This feature would need a test then,
which is no usual micro benchmark.

So I think it is a good idea to avoid to introduce slow operations in
hot code path, but it does not help much the developers in the problem of
simulating workload and measuring the interactive and real throughput.

But perhaps you can take this into account?

Greetings
Bernd

  reply	other threads:[~2002-08-12  1:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-11 20:17 Mel
2002-08-12  1:40 ` Bernd Eckenfels [this message]
2002-08-12  9:27   ` Daniel Phillips
2002-08-12 14:06     ` Rik van Riel
2002-08-12 16:06       ` Mel
2002-08-12 16:13         ` Rik van Riel
2002-08-12 16:36           ` Mel
2002-08-13  7:43       ` Helge Hafting
2002-08-12 11:33   ` Mel

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=E17e4C2-0005yH-00@sites.inka.de \
    --to=ecki-news2002-08@lina.inka.de \
    --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

all inboxes | Powered by JetHome®