public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4 vs 2.2 performance under load comparison
Date: Thu, 22 Feb 2001 13:54:40 +0100	[thread overview]
Message-ID: <20010222135440.M1320@marowsky-bree.de> (raw)

Good morning,

I did a comparison between 2.4 and 2.2.18 (+ Andrea's patches), using the
respective latest SuSE kernels, but the results should apply to the versions
in general.

Situation: SAP R/3 + SAP DB + benchmark driver running on a single node 4 CPU
SMP machine, tuned down to 1GB of RAM.

Running the SAP benchmark with 75 users on 2.2 yields for the first benchmark
run:

- 7018ms average response time
- 2967s CPU time in 1136s elapsed time
- ~500MB swap allocated
- ~1500 pages paged in/s, 268 pages/out/s on average

Running the same benchmark on 2.4:

- ~700ms average response time
- 1884s CPU time in 669s elapsed time
- ~500MB swap allocated
- ~50 pages paged in, ~212 pages paged out per second on average

Running the same benchmark the second time on both machines to get them warmed
up, 2.2 stays in approximately the same range, while 2.4 gets even _better_,
dropping down to ~350ms response time and ~20 pages in/out.

This is a rather amazing improvement in swapping performance.

Rik, it's time for you to break it again *g*

Sincerely,
    Lars Marowsky-Brée <lars.marowsky-bree@sap.com>
    SuSE Linux AG at the SAP LinuxLab - lmb@suse.de

-- 
Perfection is our goal, excellence will be tolerated. -- J. Yahl


             reply	other threads:[~2001-02-22 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 12:54 Lars Marowsky-Bree [this message]
2001-02-23  5:03 ` 2.4 vs 2.2 performance under load comparison Rik van Riel

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=20010222135440.M1320@marowsky-bree.de \
    --to=lmb@suse.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