FYI, this popped up today on my box running v24.6 (while I know it is 99.9% likely nothing, I figured that if others got much of this too...)

[code][Sat Dec 18 05:42:22 2004]
Iteration: 1231419/12898861, ERROR: ROUND OFF (0.4213256836) > 0.40
Continuing from last save file.
[Sat Dec 18 11:23:45 2004]
Disregard last error. Result is reproducible and thus not a hardware problem.
For added safety, redoing iteration using a slower, more reliable method.
Continuing from last save file.[/code]and before the start of the run on this expo[code]Trying 1000 iterations for exponent 12898861 using 640K FFT.
If average roundoff error is above 0.24166, then a larger FFT will be used.
Final average roundoff error is 0.24111, using 640K FFT for exponent 12898861.[/code]

[QUOTE=sdbardwick]stippix, by "2 threads in parallel" do you mean you have 2 instances of Prime95 running simultaneously?
If so, is processor affinity set correctly? Just asking, because I get very little increase in iteration time when running two processes compared to one. (24.6, 2x MP1900+, 256K L2)
M20996011: 119 ms/it for 1 instance, 123 ms/it on each of 2 instances[/QUOTE]

Hi!

Yes, 2 threads in parallel stands for 2 instances of Prime95 running in parallel, so that every cpu is running one instance.
Affinity does not do too much with version 24.6 - if I set it, then there is an improvement of only 1.7 percent. In the older versions (22.12, 23.8) the improvement by setting affinity was better (roughly 4.3-5.9 percent).

But that only means - at least on my system - that it should not be necessary to set affinity any more for version 24.6 ...

greetings stippix

hi!

I post the benchmark for my duron 1600 OC at 2100 Mhz.The speed gain is impressive !!! :showoff: :bounce: :showoff:
My cpu is still stable with v24.6 without increasing core voltage (1.55, the max with a asrock mobo).

Best regards.
Philippe.

AMD Duron(tm)
CPU speed: 2099.79 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size: 64 KB
L2 cache size: 64 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 256
Prime95 version 23.8, RdtscTiming=1
Best time for 512K FFT length: 44.475 ms.
Best time for 640K FFT length: 60.051 ms.
Best time for 768K FFT length: 74.685 ms.
Best time for 896K FFT length: 91.446 ms.
Best time for 1024K FFT length: 108.331 ms.
Best time for 1280K FFT length: 149.731 ms.
Best time for 1536K FFT length: 191.390 ms.
Best time for 1792K FFT length: 232.729 ms.
Best time for 2048K FFT length: 266.819 ms.

AMD Duron(tm)
CPU speed: 2099.90 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size: 64 KB
L2 cache size: 64 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 256
Prime95 version 24.6, RdtscTiming=1
Best time for 512K FFT length: 31.396 ms.
Best time for 640K FFT length: 42.377 ms.
Best time for 768K FFT length: 51.444 ms.
Best time for 896K FFT length: 68.410 ms.
Best time for 1024K FFT length: 89.588 ms.
Best time for 1280K FFT length: 109.108 ms.
Best time for 1536K FFT length: 131.276 ms.
Best time for 1792K FFT length: 158.702 ms.
Best time for 2048K FFT length: 178.855 ms.

Goodbye.

[QUOTE=Uncwilly]FYI, this popped up today on my box running v24.6 (while I know it is 99.9% likely nothing, I figured that if others got much of this too...)

[code][Sat Dec 18 05:42:22 2004]
Iteration: 1231419/12898861, ERROR: ROUND OFF (0.4213256836) > 0.40
Continuing from last save file.
[Sat Dec 18 11:23:45 2004]
Disregard last error. Result is reproducible and thus not a hardware problem.
For added safety, redoing iteration using a slower, more reliable method.
Continuing from last save file.[/code][/quote]Got it again,[code][Sun Dec 19 13:31:14 2004]
Iteration: 2101873/12898861, ERROR: ROUND OFF (0.4157104492) > 0.40
Continuing from last save file.
[Sun Dec 19 17:35:51 2004]
Disregard last error. Result is reproducible and thus not a hardware problem.
For added safety, redoing iteration using a slower, more reliable method.
Continuing from last save file.[/code]

Uncwilly,
I assume you are using a non-P4. The exponent you have chosen is very close to an FFT limit. Prime95 uses 12890000 as the point at which non-P4s switch from the 640K to 768K FFTs. However as of version 22 it uses soft crossover - read about it in undoc.txt
Near the FFT boundaries, it is not uncommon to get these errors and if you get a "Disregard error" message, everything is okay. So worry only if you DO NOT get a "Disregard" message.

I see from your posts that you lost about 5 hours of processing each time. So you may want to reduce the "time between disk writes" to 30 minutes while you do exponents in this range.

[QUOTE=garo]I assume you are using a non-P4. The exponent you have chosen is very close to an FFT limit. Prime95 uses 12890000 as the point at which non-P4s switch from the 640K to 768K FFTs. However as of version 22 it uses soft crossover - read about it in undoc.txt
Near the FFT boundaries, it is not uncommon to get these errors and if you get a "Disregard error" message, everything is okay. So worry only if you DO NOT get a "Disregard" message.

I see from your posts that you lost about 5 hours of processing each time. So you may want to reduce the "time between disk writes" to 30 minutes while you do exponents in this range.[/QUOTE]

I am running an Athlon. I did chang my disk write from 360 to 60 minutes. Maybe for the duration of this expo I will set it even lower.


BTW I got another one.

[QUOTE=delta_t]Just started a double-check with the new v24.6.
DoubleCheck=13157663,64,1[/QUOTE]

Forgot to mention that the Athlon machine running a DC (above) with 24.6 finished a few days ago, could someone check if it matched the other result?

[QUOTE=delta_t]Forgot to mention that the Athlon machine running a DC (above) with 24.6 finished a few days ago, could someone check if it matched the other result?[/QUOTE]

It matched!

Are there any TF improvements in v24?

I can reasonably conclude that there is a slight increase in power usage with the new version on at least the T-bred B, Barton, and palomino chips. It’s negligible (less than .25v in almost all cases), but present.

This isn’t anything to get super worried about. When I did the tests, I would run the chips at the absolute minimum voltage to remain stable. Most K7 machines run chips at recommended voltage, which is well beyond this power usage increase, but computers with shotty power systems might feel the crunch this time.

[QUOTE=Xyzzy]Mprime on a K8...

AMD Athlon(tm) 64 Processor 3400+
CPU speed: 2402.69 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE, SSE2
L1 cache size: 64 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 512
Prime95 version [b]24.6[/b], RdtscTiming=1
Best time for 4K FFT length: 0.093 ms.
Best time for 5K FFT length: 0.133 ms.
Best time for 6K FFT length: 0.168 ms.
Best time for 7K FFT length: 0.211 ms.
Best time for 8K FFT length: 0.235 ms.
Best time for 10K FFT length: 0.311 ms.
Best time for 12K FFT length: 0.361 ms.
Best time for 14K FFT length: 0.451 ms.
Best time for 16K FFT length: 0.514 ms.
Best time for 20K FFT length: 0.651 ms.
Best time for 24K FFT length: 0.787 ms.
Best time for 28K FFT length: 0.957 ms.
Best time for 32K FFT length: 1.065 ms.
Best time for 40K FFT length: 1.723 ms.
Best time for 48K FFT length: 2.120 ms.
Best time for 56K FFT length: 2.577 ms.
Best time for 64K FFT length: 2.946 ms.
Best time for 80K FFT length: 3.904 ms.
Best time for 96K FFT length: 4.733 ms.
Best time for 112K FFT length: 5.672 ms.
Best time for 128K FFT length: 6.513 ms.
Best time for 160K FFT length: 8.105 ms.
Best time for 192K FFT length: 9.764 ms.
Best time for 224K FFT length: 11.655 ms.
Best time for 256K FFT length: 13.041 ms.
Best time for 320K FFT length: 17.041 ms.
Best time for 384K FFT length: 20.524 ms.
Best time for 448K FFT length: 24.493 ms.
Best time for 512K FFT length: 27.615 ms.
Best time for 640K FFT length: 34.023 ms.
Best time for 768K FFT length: 41.731 ms.
Best time for 896K FFT length: 50.227 ms.
Best time for 1024K FFT length: 56.740 ms.
Best time for 1280K FFT length: 75.799 ms.
Best time for 1536K FFT length: 90.789 ms.
Best time for 1792K FFT length: 110.390 ms.
Best time for 2048K FFT length: 125.055 ms.
Best time for 2560K FFT length: 163.044 ms.
Best time for 3072K FFT length: 187.716 ms.
Best time for 3584K FFT length: 232.004 ms.
Best time for 4096K FFT length: 266.159 ms.

AMD Athlon(tm) 64 Processor 3400+
CPU speed: 2402.39 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE, SSE2
L1 cache size: 64 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 512
Prime95 version [b]23.9[/b], RdtscTiming=1
Best time for 384K FFT length: 20.539 ms.
Best time for 448K FFT length: 24.491 ms.
Best time for 512K FFT length: 27.511 ms.
Best time for 640K FFT length: 34.074 ms.
Best time for 768K FFT length: 41.511 ms.
Best time for 896K FFT length: 49.847 ms.
Best time for 1024K FFT length: 56.590 ms.
Best time for 1280K FFT length: 75.263 ms.
Best time for 1536K FFT length: 90.542 ms.
Best time for 1792K FFT length: 109.816 ms.
Best time for 2048K FFT length: 124.190 ms.
Best time for 2560K FFT length: 162.746 ms.
Best time for 3072K FFT length: 187.725 ms.
Best time for 3584K FFT length: 230.422 ms.
Best time for 4096K FFT length: 266.172 ms.[/QUOTE]

Hi!

Xyzzy could you tell me how you got all these different FFT-length. I only get 9 different values in 24.6 ranging from 512K to 2048K.

greetings stippix