public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grecko OSCP <grecko.lists@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Linux Kernel Performance Testing
Date: Fri, 1 Apr 2005 11:22:20 -0700	[thread overview]
Message-ID: <1c55c94505040110224ea1ebb6@mail.gmail.com> (raw)

Hey All,

I noticed yesterday a news article on Linux.org about more kernel
performance testing being called for, and I decided it would be a nice
project to try. I have 10 completely identical systems that can be
used for this, and would like to get started while I know I have them
for a while.

However, I wanted to make sure I didn't waste time. My plan was to do
all testing, prerelease, and release kernels from the 2.4, 2.5, and
2.6 trees, with both lmbench and the Linux Testing Project (LTP)
benchmark suite. Will this help out? Is there anything else a person
should do? With those two benchmarks, and all the kernels I mentioned,
I could be done in about 25 days, at one kernel a machine a day. I
assume it wouldn't matter what distribution was used, so long as its
the same for all tests?

Thanks!
Grecko

             reply	other threads:[~2005-04-01 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01 18:22 Grecko OSCP [this message]
2005-04-01 23:56 ` Linux Kernel Performance Testing Chen, Kenneth W

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=1c55c94505040110224ea1ebb6@mail.gmail.com \
    --to=grecko.lists@gmail.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