mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: cliff white <cliffw@osdl.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: reaim - 2.6.3-mm1 IO performance down.
Date: Tue, 24 Feb 2004 16:20:52 -0800	[thread overview]
Message-ID: <20040224162052.33895550.cliffw@osdl.org> (raw)



Running the reaim 'new_fserver' workload, we now see a performance drop
on 2.6.3-mm1, ext3 filesystem

Kernel          JPM       Max Users     Percent change
inux-2.6.3      10347.87  172           0.0
2.6.3-rc3-mm1   9826.35   164           -5.07
2.6.3-mm1       8938.17   140   (run 1) -13.65
2.6.3-mm1       9100.39   136    (run 2)-12.08 

I have done some comparions graphs here, with readprofile data:
http://developer.osdl.org/cliffw/reaim/compares/r_comp/2.6.3_vs_mm1_r1/index.html
http://developer.osdl.org/cliffw/reaim/compares/r_comp/2.6.3_vs_mm1_r2/index.html

The interesting graph is the bottom one on the page, comparing client
run-time to number of children. The -mm1 kernel has a spike in run time, becoming
very noticealbe around 60-80 lusers.

kernel       Users 	JPM        Run Time
linux-2.6.3  60         10327.87   34.16 seconds
2.6.3-mm1    60         8279.75    42.61 seconds

Linux-2.6.3  80         10275.23   45.78 seconds
2.6.3-mm1    80         7841.31    59.99 seconds


For the same test on the same machine, results from 2.6.2-rc1-mm2 and 2.6.2-rc3-mm1
were within 1.0% of the linux-2.6.2 runs. So this is new. 

More data and tests if requested - are there some patch sets we should try reverting?
cliffw

-- 
The church is near, but the road is icy.
The bar is far, but i will walk carefully. - Russian proverb

             reply	other threads:[~2004-02-25  0:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  0:20 cliff white [this message]
2004-02-25  1:03 ` Andrew Morton
2004-02-25 17:40   ` Cliff White
2004-02-25 19:16     ` Andrew Morton
2004-02-25 20:52       ` Cliff White
2004-02-25 23:36   ` Cliff White
2004-02-25  2:00 Con Kolivas
2004-02-25  3:31 ` Nick Piggin

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=20040224162052.33895550.cliffw@osdl.org \
    --to=cliffw@osdl.org \
    --cc=akpm@osdl.org \
    --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®