public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Reasonable L1 cache miss rate for gcc
Date: Sun, 11 Aug 2002 09:02:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0208111200450.3327-100000@dberlin.org> (raw)
In-Reply-To: <20020811152045.GA3379@nevyn.them.org>

On Sun, 11 Aug 2002, Daniel Jacobowitz wrote:

> On Sun, Aug 11, 2002 at 01:12:39AM -0400, Daniel Berlin wrote:
> > What is a reasonable L1 cache miss rate (for memory loads 
> > only not instructions) is for a P4 running GCC?
> > 
> > I have the exact figures, but without some idea of what reasonable would 
> > be, i have no idea how *bad* it is.
> > 
> > Percentage wise, it's a 14-25% miss rate (depending on input).
> > 
> > Of course, I really want to know about L2's, but the file describing all  
> > the available p4 pmcs says:
> 
> > Sigh.
> > 
> > Someone with a PIII should be able to get oprofile to give us some l2 
> > numbers.
> 
> Assuming that I actually figured out what these numbers mean...
> I remade insn-*.o in a gcc HEAD build with two compilers (no
> optimization):
> 
> 		DATA_MEM_REFS		L2_LINES_IN	  L2 Miss %
> GCC 2.95.3 cc1	 4.32e9			  3.23e7	  0.7%
> GCC 3.1.1 cc1	 7.0265e9		  6.3e7		  0.8%
> 
> Something tells me I've got the wrong numbers, though... those look far
> too low.  If someone cares to enlighten me on the right counters to
> use, I'll be more thorough.

Make sure it compiles with optimization on.

But, otherwise, it's quite possible those aren't too low.
Remember it can only take an L2 miss when it misses L1.
So comparing complete data refs to L2 misses will always give you very 
low numbers.

      reply	other threads:[~2002-08-11  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-10 22:12 Daniel Berlin
2002-08-11  8:20 ` Daniel Jacobowitz
2002-08-11  9:02   ` Daniel Berlin [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=Pine.LNX.4.44.0208111200450.3327-100000@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=drow@false.org \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).