From: Brian Gerst <bgerst@didntduck.org>
To: "Willi Nüßer" <wilhelm.nuesser@sap.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Comparison of PAE and Non-PAE 2..4.14 (p8) in high load
Date: Wed, 14 Nov 2001 09:45:15 -0500 [thread overview]
Message-ID: <3BF2837B.4B63FBA5@didntduck.org> (raw)
In-Reply-To: <3BF27557.30007@sap.com>
Willi Nüßer wrote:
>
> Hi,
>
> after my first posting to lkml where we compared distributor
> provided kernels vs. a plain 2.4.14-pre8 it was pointed
> out that between PAE and non-PAE kernels some performance
> differences might exist.
>
> We checked this last night and here are the first results.
> Again,
> a) the relevant quantity dialog steps per second is a
> measure for the throughput our application servers runs.
> b) our application server and the corresponding database
> (SAP DB) run on 4 way Dell, 1 GB at boot time enabled.
>
> Results:
> ---------
>
> 2.4.7
> 2.4.14p8 PAE 2.4.14p4 non- PAE
> -------------------------------------------------------------
> 1.80 13.42 15.47
> 1.10 13.28 14.76
> 1.20 14.08 14.63
> 1.26 13.17 15.30
> 1.35 13.41 14.51
>
> This means that we did see a performance decrease of about
> 6 % compared to 2.4.14p8 nonPAE but still 2.4.14p8 is an order
> of magnitude faster than 2.4.7
PAE mode increases the size of the page table entries to 64-bits, and
the x86 doesn't do 64-bit operations very well. Plus it has three
levels of tables to work with instead of two. It is the only way to
support more than 4GB of memory so it's a tradeoff between high memory
support and performance. If you have less memory, don't run a PAE
kernel.
--
Brian Gerst
next prev parent reply other threads:[~2001-11-14 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 13:44 Comparison of PAE and Non-PAE 2..4.14 (p8) in high load Willi Nüßer
2001-11-14 14:45 ` Brian Gerst [this message]
2001-11-14 15:36 ` Willi Nüßer
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=3BF2837B.4B63FBA5@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wilhelm.nuesser@sap.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