mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gerrit Huizenga <gh@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: "Reed, Timothy A" <timothy.a.reed@lmco.com>,
	"Linux Kernel ML (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: High Mem Options
Date: Wed, 05 Mar 2003 13:11:25 -0800	[thread overview]
Message-ID: <E18qgAh-00033w-00@w-gerrit2> (raw)
In-Reply-To: Your message of Wed, 05 Mar 2003 12:58:49 PST. <20030305205849.GU1195@holomorphy.com>

On Wed, 05 Mar 2003 12:58:49 PST, William Lee Irwin III wrote:
> On Wed, 05 Mar 2003 04:26:54 PST, William Lee Irwin III wrote:
> >> Yes, the additional level of pagetables slows things down quite a bit.
> 
> On Wed, Mar 05, 2003 at 12:31:03PM -0800, Gerrit Huizenga wrote:
> > Bill, do you hvae measures for this?  I seem to remember PTX's impact
> > of PAE36 as being about 3-5% depending on workload.  Janet did one test
> > sometime back with DB2 that showed a net of no difference on TPC-H (PAE
> > slows things down, less memory pressure speeds things up) but Badari
> > just repeated with 2.5.62 or 2.5.63 and saw a larger degradation.
> > I'm wondering if some hardware is not getting correctly configured at
> > boot with with respect to MTRR's, perhaps...  I really wouldn't expect
> > a 10% impact from PAE and I don't have any consistent Linux measurements
> > to validate or invalidate that much impact.
> 
> Unfortunately the number of ca. 10% I got from you. I think badari's
> done some $BENCHMARK_THAT_CANNOT_BE_NAMED things recently that were
> consistent with the handwavy estimate but AIUI they were not intended
> to measure the effect etc. etc.

Ah, if you are referring to a number from me, that was with 2.4 and
that number seemed high to me at the time.  I don't believe that 10%
*should* be the amount of degradation.  But I don't have current numbers
(that I can share, anyway ;-) that prove anything less than that.

I expect that we'll be diving into this more over the next few months
as we can generate some large workloads and find the cause of the
degradation (and hopefully minimize it).

gerrit

  reply	other threads:[~2003-03-05 21:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 11:28 Reed, Timothy A
2003-03-05 12:11 ` Michael Vergoz
2003-03-05 13:36   ` Alan Cox
2003-03-05 12:49     ` Michael Vergoz
2003-03-05 12:57       ` William Lee Irwin III
2003-03-05 13:02         ` Michael Vergoz
2003-03-05 13:10           ` William Lee Irwin III
2003-03-09  2:41           ` Bill Davidsen
2003-03-05 14:21       ` Alan Cox
2003-03-05 12:26 ` William Lee Irwin III
2003-03-05 20:31   ` Gerrit Huizenga
2003-03-05 20:58     ` William Lee Irwin III
2003-03-05 21:11       ` Gerrit Huizenga [this message]
2003-03-05 21:34         ` Martin J. Bligh
2003-03-05 13:38 ` Alan Cox

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=E18qgAh-00033w-00@w-gerrit2 \
    --to=gh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timothy.a.reed@lmco.com \
    --cc=wli@holomorphy.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

all inboxes | Powered by JetHome®