From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [RFC] 4-level page table directories.
Date: Fri, 04 Nov 2005 21:42:41 +0000 [thread overview]
Message-ID: <200511042142.jA4Lgfg14906@unix-os.sc.intel.com> (raw)
In-Reply-To: <20051027041709.GA13193@attica.americas.sgi.com>
Robin Holt wrote on Friday, November 04, 2005 1:38 PM
> On Fri, Nov 04, 2005 at 10:51:07AM -0800, Chen, Kenneth W wrote:
> > Luck, Tony wrote on Wednesday, November 02, 2005 8:31 AM
> > > Good to hear that (though I must remember to specify what I mean
> > > by "small memory" when talking to SGI ... there are ia64 boxes
> > > with only 1G :-)
> > >
> > > Ken: Any predictions on when a 4-level run might get to the
> > > top of your queue for a run with an industry standard transaction
> > > benchmark?
> >
> > It turns out that we have measurable performance regression with
> > 4-level page table running industry database benchmark, the penalty
> > is ~0.2% (I thought the number would be smaller than 0.2%, but ...).
> > Our resolution with this workload is typically 0.05%.
>
> Can you point me at this benchmark?
I hope everyone knows by now what this "industry standard database
transaction processing benchmark" is. If not, please google it.
Sorry, this is the best I can do without breaking any U.S. law.
- Ken
next prev parent reply other threads:[~2005-11-04 21:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 4:17 [RFC] 4-level page table directories Robin Holt
2005-10-28 5:19 ` Ian Wienand
2005-10-28 11:19 ` Robin Holt
2005-10-28 23:23 ` Luck, Tony
2005-10-28 23:55 ` Chen, Kenneth W
2005-10-29 0:49 ` Grant Grundler
2005-10-29 2:18 ` David Mosberger-Tang
2005-11-01 12:13 ` Robin Holt
2005-11-01 15:41 ` David Mosberger-Tang
2005-11-02 10:35 ` Robin Holt
2005-11-02 13:26 ` Robin Holt
2005-11-02 16:11 ` Luck, Tony
2005-11-02 16:23 ` Robin Holt
2005-11-02 16:30 ` Luck, Tony
2005-11-02 17:16 ` Robin Holt
2005-11-02 18:59 ` David Mosberger-Tang
2005-11-02 22:26 ` Ian Wienand
2005-11-03 1:36 ` Gerald Pfeifer
2005-11-03 1:53 ` Chen, Kenneth W
2005-11-03 3:55 ` Jack Steiner
2005-11-03 16:36 ` Robin Holt
2005-11-03 19:59 ` Chen, Kenneth W
2005-11-04 17:58 ` Luck, Tony
2005-11-04 21:37 ` Robin Holt
2005-11-04 21:42 ` Chen, Kenneth W [this message]
2005-11-04 22:50 ` Chen, Kenneth W
2005-11-07 21:18 ` Luck, Tony
2005-11-08 0:22 ` Rohit Seth
2005-11-08 12:43 ` Robin Holt
2005-11-08 18:23 ` Boehm, Hans
2005-11-08 18:52 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-08 18:56 ` Rohit Seth
2005-11-08 19:36 ` Robin Holt
2005-11-08 20:07 ` Chen, Kenneth W
2005-11-08 20:27 ` Chen, Kenneth W
2005-11-08 22:09 ` Ian Wienand
2005-11-08 23:58 ` Gerald Pfeifer
2005-11-09 0:08 ` David Mosberger-Tang
2005-11-09 0:22 ` Rohit Seth
2005-11-09 0:46 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-11-09 1:18 ` Chen, Kenneth W
2005-11-09 12:11 ` Robin Holt
2005-11-09 14:29 ` Robin Holt
2005-11-09 18:22 ` Chen, Kenneth W
2005-11-09 18:39 ` Luck, Tony
2005-11-10 0:03 ` Gerald Pfeifer
2005-11-10 0:23 ` Jack Steiner
2005-11-10 0:27 ` Luck, Tony
2005-11-10 2:54 ` Jack Steiner
2005-11-10 9:13 ` Robin Holt
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=200511042142.jA4Lgfg14906@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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