All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arvid Ericsson <aquid@linux.nu>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Memory performance significantly improved w/ 2.4.1ac11
Date: Wed, 14 Feb 2001 14:39:56 +0100	[thread overview]
Message-ID: <3A8A8AAC.C04F8C2@linux.nu> (raw)
In-Reply-To: <Pine.LNX.4.10.10102141026080.12204-100000@coffee.psychology.mcmaster.ca>

Mark Hahn skrev:
> first, are you sure your clock is write?  the changes appear
> to be tiny ~2 MB/s, and might be explained by the fact that
> 2.2 and 2.4 have different implementations of gettimeofday.

The change I was happy about was the one between 2.4.0ac10 and
2.4.1ac11. I think that it's a good thing that a few percent more memory
bandwidth appears from nowhere... Well, but that's just me I guess.

> (I'm assuming you're using gtod (second_wall.c) rather than
> a times-based measure.  the latter will be far less accurate.)

*Scratching my head* I have no idea of what your're talking about.
Sorry. Im using stream_whatever.cpp and whatever might be in it.

> 
> are you also aware that more modern compilers (2.95.2, I think)
> have more specific CPU tunings than just -mpentium?

I just used the suggested optimizations.
 
> 
> by "cycle length = 2", do you mean "tCAS latency = 2"?

Not quite sure, that the BIOS says "sdram cycle length=2" is all I know.

> finally (and don't take offense), those are astonishingly low
> Stream scores.  it's been a while since I ran Stream on a p5-class
> machine, but jeeze!  my dirt-cheap duron/600/kt133/pc133 sustains
> 600 MB/s!

Oh-well, I guess I just have a even dirt-cheaper machine than you. I
haven't got any idea of how machines similar to mine perform. 

/Arvid


       reply	other threads:[~2001-02-14 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10102141026080.12204-100000@coffee.psychology.mcmaster.ca>
2001-02-14 13:39 ` Arvid Ericsson [this message]
2001-02-14 10:30 Memory performance significantly improved w/ 2.4.1ac11 Arvid Ericsson

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=3A8A8AAC.C04F8C2@linux.nu \
    --to=aquid@linux.nu \
    --cc=hahn@coffee.psychology.mcmaster.ca \
    --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.