Innacurate benchmarks

fuzzfuzz · 2002-11-06, 22:10

This morning I downloaded 22.11 version of Prime95 to install on my work Athlon, with the intent of running Trial Factoring.

I ran the benchmark on this to see how it compares to my AthlonXP 1800 @ home, and received some very odd results. The results are also reproduceable.

System is XP 1600, 256MB of SDR RAM, Windows XP.

AMD Athlon(tm) XP 1600+
CPU speed 1400.13 MHz
CPU features RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size 64 KB
L2 cache size 256 KB
L1 cache line size 64 bytes
L2 cache line size 64 bytes
L1 TLBS 32
L2 TLBS 256
Prime95 version 22.11, RdtscTiming=1
Best time for 256K FFT length 6.659 ms.
Best time for 320K FFT length 7.500 ms.
Best time for 384K FFT length 14.703 ms.
Best time for 448K FFT length 15.000 ms.
Best time for 512K FFT length 15.000 ms.
Best time for 640K FFT length 15.000 ms.
Best time for 768K FFT length 22.500 ms.
Best time for 896K FFT length 22.500 ms.
Best time for 1024K FFT length 27.300 ms.
Best time for 1280K FFT length 35.189 ms.
Best time for 1536K FFT length 37.847 ms.
Best time for 1792K FFT length 55.479 ms.

Any ideas on what would be causing this ?

Deamiter · 2002-11-07, 09:29

I've produced benchmarks like this, but only when my computer was being stressed by a seperate program during the test. Seems like it'd probably be too simple, but are you running any other programs during the benchmark?

fuzzfuzz · 2002-11-07, 10:26

No. I cant see anything else running other than the default XP stuff.

The issue shows up while the PC is actually factoring - every line of output, it displays the time, percent etc... the time might increase by 4 minutes or so, but the time taken to actually complete the step is only something like 45 seconds. Really strange.

2002-11-06, 22:10	#1
fuzzfuzz Aug 2002 3² Posts	Innacurate benchmarks This morning I downloaded 22.11 version of Prime95 to install on my work Athlon, with the intent of running Trial Factoring. I ran the benchmark on this to see how it compares to my AthlonXP 1800 @ home, and received some very odd results. The results are also reproduceable. System is XP 1600, 256MB of SDR RAM, Windows XP. AMD Athlon(tm) XP 1600+ CPU speed 1400.13 MHz CPU features RDTSC, CMOV, PREFETCH, MMX, SSE L1 cache size 64 KB L2 cache size 256 KB L1 cache line size 64 bytes L2 cache line size 64 bytes L1 TLBS 32 L2 TLBS 256 Prime95 version 22.11, RdtscTiming=1 Best time for 256K FFT length 6.659 ms. Best time for 320K FFT length 7.500 ms. Best time for 384K FFT length 14.703 ms. Best time for 448K FFT length 15.000 ms. Best time for 512K FFT length 15.000 ms. Best time for 640K FFT length 15.000 ms. Best time for 768K FFT length 22.500 ms. Best time for 896K FFT length 22.500 ms. Best time for 1024K FFT length 27.300 ms. Best time for 1280K FFT length 35.189 ms. Best time for 1536K FFT length 37.847 ms. Best time for 1792K FFT length 55.479 ms. Any ideas on what would be causing this ?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Benchmarks	Pjetrode	Information & Answers	3	2018-01-07 23:23
Where are the Benchmarks	Sandman192	Homework Help	17	2012-04-05 19:03
Benchmarks	MurrayInfoSys	Information & Answers	3	2011-04-14 17:10
Benchmarks for 24.12	Prime95	Software	60	2005-06-11 07:35
Benchmarks	Vandy	Hardware	6	2002-10-28 13:45

2002-11-07, 09:29	#2
Deamiter Sep 2002 1110101₂ Posts	I've produced benchmarks like this, but only when my computer was being stressed by a seperate program during the test. Seems like it'd probably be too simple, but are you running any other programs during the benchmark?

2002-11-07, 10:26	#3
fuzzfuzz Aug 2002 3² Posts	No. I cant see anything else running other than the default XP stuff. The issue shows up while the PC is actually factoring - every line of output, it displays the time, percent etc... the time might increase by 4 minutes or so, but the time taken to actually complete the step is only something like 45 seconds. Really strange.