All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] page size > 16KB
Date: Fri, 14 Mar 2003 19:00:36 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806107@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806057@msgid-missing>

On Fri, Mar 14, 2003 at 09:33:30AM -0800, Jesse Barnes wrote:
> On Fri, Mar 14, 2003 at 01:33:12PM +0100, Jan Schreckenbach wrote:
> > yep, I'm doing some benchmark stuff with SAP/SAPDB and the performance
> > is not as good as I expected. CONFIG_HUGETLB_PAGE=y is standard on a
> > SLES8 kernel (2.4.19-SMP). I changed the page size from 16K to 64K
> > and the performance increase was 2-3 percent. Changing  Huge TLB Page 
> > Size" seems not to have any effect.

richa pointed out that it would probably be a good idea to use perfmon
to count L2DTLB_MISSES events for your app to see whether TLB misses
are really causing a problem.  Another good thing to do might be to
run vmstat during your app run to see how much I/O wait time you're
seeing, and whether you're saturating your block device, etc.

Jesse


  parent reply	other threads:[~2003-03-14 19:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 16:38 [Linux-ia64] page size > 16KB Jan Schreckenbach
2003-03-12 16:55 ` Grant Grundler
2003-03-12 17:07 ` n0ano
2003-03-12 17:40 ` David Mosberger
2003-03-12 17:46 ` David Mosberger
2003-03-12 17:49 ` Jesse Barnes
2003-03-12 18:07 ` David Mosberger
2003-03-12 18:08 ` Grant Grundler
2003-03-12 18:24 ` Jesse Barnes
2003-03-12 19:51 ` Mario Smarduch
2003-03-13 18:05 ` David Mosberger
2003-03-13 20:44 ` Mario Smarduch
2003-03-14 12:33 ` Jan Schreckenbach
2003-03-14 15:51 ` Chen, Kenneth W
2003-03-14 17:33 ` Jesse Barnes
2003-03-14 18:00 ` Mario Smarduch
2003-03-14 18:17 ` Grant Grundler
2003-03-14 19:00 ` Jesse Barnes [this message]
2003-03-14 19:43 ` David Mosberger
2003-03-15  3:08 ` Seth, Rohit

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=marc-linux-ia64-105590709806107@msgid-missing \
    --to=jbarnes@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.