At 03:26 18.06.2001, you wrote:
Hi all,
Now the bad news. The Athlon also supports these memory prefetch
instructions but the one user who tried it reported no gain. Also, the new
executable may also be slightly slower on the P-II and Celeron 1 as it must
ignore these prefetch
Hi All,
I downloaded and ran the new v21a and did some timings on
several different machines and compared them to timings done
on v19 and v20...
I ran the timings on each version for 100 screen outputs at
100 iterations per screen output... for a total of 1
iterations... and then
From: George Woltman
I've added these hints to prime95 and
am getting about a 20% performance boost.
My turn to report! :-)
v20v21
--
p3/850 0.301 0.215
p3/515 0.398 0.309
The 515 is a slightly overclocked 500Mhz processor. Both machines are
running
H,
I am not getting any performance increase on my 2 Athlon's here, and I am
99% sure they are Thunderbirds.
I just tried this new executable on 7 machines. Here are the numbers.
PentiumIII 450MHz Testing M12441xxx
Iteration Times
V.20V.21
0.330 0.255
PentiumII
H,
I am not getting any performance increase on my 2 Athlon's here, and I am
99% sure they are Thunderbirds.
It appears I was wrong, the prefetch is available on all Athlons not just
Thunderbirds, so it must be something else.
Michael.
One more possibility to keep in mind for Athlons: BIOS level
(and perhaps also which motherboard).
Don't have windows, so can't try the optimized prime95, but
have noticed on timing runs with the V20 mprime that my new
(ASUS A7M266) Athlon is now 2% slower than when I first got it.
The only
Hi,
At 01:43 AM 6/19/2001 +0100, Michael Bell wrote:
I am not getting any performance increase on my 2 Athlon's here, and I am
99% sure they are Thunderbirds.
Some Athlons are seeing a speed increase others are not. The two
that I know are not enjoying a speed increase are running under
My 1 GHz Thunderbird in Win98 SE showed speed improvements without putting
anything in the .ini file. I used the Advanced-Time option and noted the
following two anomalies:
1) At 512 KB and only 512 KB, the program returned the following along with
my timings:
timer 0: 1100364
timer 1:
