From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Brian Twichell' <tbrian@us.ibm.com>, Dave McCracken <dmccr@us.ibm.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Linux Memory Management <linux-mm@kvack.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
slpratt@us.ibm.com
Subject: RE: [PATCH 0/2][RFC] New version of shared page tables
Date: Fri, 5 May 2006 20:37:22 -0700 [thread overview]
Message-ID: <4sur0l$vjssd@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <445BA6B2.4030807@us.ibm.com>
Brian Twichell wrote on Friday, May 05, 2006 12:26 PM
> We also measured the benefit of shared pagetables on our larger setups.
> On our 4-way x86-64 setup with 64 GB memory, using small pages for the
> bufferpools, shared pagetables provided a 33% increase in transaction
> throughput. Using hugepages for the bufferpools, shared pagetables
> provided a 3% increase. Performance with small pages and shared
> pagetables was within 4% of the performance using hugepages without
> shared pagetables.
>
> On our ppc64 setups we used both Oracle and DB2 to evaluate the benefit
> of shared pagetables. When database bufferpools were in small pages,
> shared pagetables provided an increase in database transaction
> throughput in the range of 60-65%, while in the hugepage case the
> improvement was up to 2.4%.
I would also like to add that I have run this set of patches on ia64 and
observed similar performance upside. We have multiple data points showing
that this feature benefits several architectures. I'm advocating for the
upstream inclusion.
- Ken
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2006-05-06 3:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 15:43 Dave McCracken
2006-05-03 15:56 ` Hugh Dickins
2006-05-03 16:06 ` Dave McCracken
2006-05-06 15:25 ` Hugh Dickins
2006-05-08 19:32 ` Ray Bryant
2006-05-16 21:09 ` Dave McCracken
2006-05-19 16:55 ` Ray Bryant
2006-05-22 18:00 ` Ray Bryant
2006-05-08 19:49 ` Brian Twichell
2006-05-09 3:42 ` Nick Piggin
2006-05-10 2:07 ` Chen, Kenneth W
2006-05-10 19:45 ` Brian Twichell
2006-05-12 5:17 ` Nick Piggin
2006-05-09 19:22 ` Hugh Dickins
2006-05-05 19:25 ` Brian Twichell
2006-05-06 3:37 ` Chen, Kenneth W [this message]
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='4sur0l$vjssd@fmsmga001.fm.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=dmccr@us.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=slpratt@us.ibm.com \
--cc=tbrian@us.ibm.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