All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Schein <igor@txc.com>
To: linux-kernel@vger.kernel.org
Subject: performance of cache-intensive applications
Date: Tue, 3 Dec 2002 21:08:38 -0500	[thread overview]
Message-ID: <20021204020838.GF3807@txc.com> (raw)

Hi,

I am using an open-source application on ix86 to perform a task which
is cache-intensive.  When I run consecutive iterations of the task on
a fixed input, the variance in timing of each iteration is extemely
high.   Needless to say, the test machine is always non-occupied.

On every other OS I tried, Solaris, HPUX, FreeBSD and Tru64, the
timing is very consistent between the iterations.  My question is, are
there known issues with L2 cache reuse in Linux kernel?

I can provide any necessary information for anyone interested in
addressing this issue, but I purposely skipped most technical details
in this post to keep it simple.

Thanks in advance.

Igor


             reply	other threads:[~2002-12-04  2:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04  2:08 Igor Schein [this message]
2002-12-04  8:56 ` performance of cache-intensive applications Giuliano Pochini
  -- strict thread matches above, loose matches on Subject: below --
2002-12-04  2:17 Nakajima, Jun

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=20021204020838.GF3807@txc.com \
    --to=igor@txc.com \
    --cc=linux-kernel@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.