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

[QUOTE=Prime95]It matched![/QUOTE]

I hope that mine did.:bow: I have watched for an update to the status page so I can check.:unsure: (This is the first time that I have actually worried about going to the effort to check.) :mellow:

Just submitted 13204339; it matched to the (partly obscured) result I found in a cleared.txt! :bounce:

[QUOTE=stippix]Xyzzy could you tell me how you got all these different FFT-length. [/QUOTE]I'm not Xyzzy, but I can quote him :smile: [QUOTE=Xyzzy]please put "FullBench=1" in prime.ini...[/QUOTE]

[QUOTE=Prime95]It matched![/QUOTE]
Excellent. A few more DC's and could we feel comfortable to run 24.6 of first time LL tests?

Two more DC completed:

UID: sdbardwick/Dual_MP_1, M13091987 is not prime. Res64: 538761BF506Bxxxx. Wa1: 4FBEC629,8870607,00000000
UID: sdbardwick/Dual_MP_0, M13091473 is not prime. Res64: 78D6F8752E17xxxx. Wa1: 408F554E,6147157,00000000

I've got a feeling that errors are more likely to occur near the high end of an FFT range (and I don't mean the reproducible errors). Has anyone made some statistics about that? So at least those of you Athlons owners who overclock and get a hotter computer should perhaps try to get hold of a few exponents below 12.83M to double-check.

Would this also be something to consider when confirming that v24.6 works correctly? I don't know.

[QUOTE=sdbardwick]Two more DC completed:

UID: sdbardwick/Dual_MP_1, M13091987 is not prime. Res64: 538761BF506Bxxxx.
UID: sdbardwick/Dual_MP_0, M13091473 is not prime. Res64: 78D6F8752E17xxxx. [/QUOTE]

Two more matches. Feel free to use 24.6 to test whatever you'd like.

[QUOTE=Uncwilly]Finished and reported a DC done ~50% with v24.6 on an athalon.

[Thu Dec 16 16:15:45 2004]
UID: Team_Inspector/uncwilly, M13328993 is not prime. Res64: xxxxxxxxxxxxxxxx. Wa1: xxxxxxxx,xxxxxxxx,00000000

res blocked out by me.[/QUOTE]

Found in cleared.txt

Maybe I will finally look at doing a 33M.... :wink:

Hello George, thanks for the new 24.6 for FreeBSD.
Here's the benches for a dual Athlon MP server running FreeBSD 5.2

[B]Old v23.5[/B]
AMD Athlon(tm) MP 2000+
CPU speed: 1666.05 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 23.5, RdtscTiming=1
Best time for 384K FFT length: 37.857 ms.
Best time for 448K FFT length: 43.859 ms.
Best time for 512K FFT length: 47.066 ms.
Best time for 640K FFT length: 62.214 ms.
Best time for 768K FFT length: 74.421 ms.
Best time for 896K FFT length: 88.771 ms.
Best time for 1024K FFT length: 99.729 ms.
Best time for 1280K FFT length: 133.427 ms.
Best time for 1536K FFT length: 157.636 ms.
Best time for 1792K FFT length: 195.026 ms.
Best time for 2048K FFT length: 221.948 ms.



[B]New v24.6[/B]
AMD Athlon(tm) MP 2000+
CPU speed: 1665.55 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 24.6, RdtscTiming=1
Best time for 512K FFT length: 39.372 ms.
Best time for 640K FFT length: 53.396 ms.
Best time for 768K FFT length: 64.537 ms.
Best time for 896K FFT length: 78.601 ms.
Best time for 1024K FFT length: 87.601 ms.
Best time for 1280K FFT length: 115.550 ms.
Best time for 1536K FFT length: 138.869 ms.
Best time for 1792K FFT length: 167.507 ms.
Best time for 2048K FFT length: 188.409 ms.

Here's a FreeBSD 5.3 server running on a Duron:

[B]Old v23.5 [/B]
AMD Duron(tm) Processor
CPU speed: 758.42 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX
L1 cache size: 64 KB
L2 cache size: 64 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 24
L2 TLBS: 256
Prime95 version 23.5, RdtscTiming=1
Best time for 384K FFT length: 77.363 ms.
Best time for 448K FFT length: 92.205 ms.
Best time for 512K FFT length: 99.708 ms.
Best time for 640K FFT length: 135.671 ms.
Best time for 768K FFT length: 167.202 ms.
Best time for 896K FFT length: 206.504 ms.
Best time for 1024K FFT length: 236.810 ms.
Best time for 1280K FFT length: 319.626 ms.
Best time for 1536K FFT length: 403.229 ms.
Best time for 1792K FFT length: 484.322 ms.
Best time for 2048K FFT length: 552.427 ms.


[B] New v24.6 [/B]
AMD Duron(tm) Processor
CPU speed: 758.15 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX
L1 cache size: 64 KB
L2 cache size: 64 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 24
L2 TLBS: 256
Prime95 version 24.6, RdtscTiming=1
Best time for 512K FFT length: 85.308 ms.
Best time for 640K FFT length: 117.577 ms.
Best time for 768K FFT length: 146.089 ms.
Best time for 896K FFT length: 190.425 ms.
Best time for 1024K FFT length: 241.382 ms.
Best time for 1280K FFT length: 292.387 ms.
Best time for 1536K FFT length: 351.645 ms.
Best time for 1792K FFT length: 417.955 ms.
Best time for 2048K FFT length: 471.501 ms.

I also played around with Prime95 vers 24.6 on Sierpinski factoring:

P4, 2.66GHz 512M DDR ram

using
PFactor=67607,2,9102371,1,48.5,1.75 ...
1024k FFT

vers 24.0.1
B1=60000, 660000: 117 minutes

vers 24.6
B1=55000, 632500: 185 minutes (varying quite a bit)

The new version seems to be quite a bit slower. Are there any changes in the implementation?

[QUOTE=biwema]I also played around with Prime95 vers 24.6 on Sierpinski factoring:

vers 24.0.1
B1=60000, 660000: 117 minutes

vers 24.6
B1=55000, 632500: 185 minutes (varying quite a bit)

The new version seems to be quite a bit slower. Are there any changes in the implementation?[/QUOTE]

No. But I thought the 1024K FFT was broken in 24.0.1. Try a smaller N that uses the 768K FFT.

Just turned in 12898861. Done with 24.6 Listed in cleared.txt only the soft errors as mentioned above.

version 23.8.1 to 24.6 test on Pentium 3 / 500 Mhz
 

I have a Pentium 3 laptop which has been running 23.8.1 successfully.
It has previously been listed in my primenet stats page under a heading Pentium 3 cpus.

I tried upgrading to 24.6 using the ftp binary.

This was successful. Timings we marginally faster on the 512k fft, marginally slower for bigger ones. Perhaps not significant difference, but that's not what I'm posting about.

Looking at results.txt I see that my system has changed from being a

Intel(R) Pentium(R) III processor
CPU speed: 497.56 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE

to a

Intel Celeron 2 (Mobile/XBOX) processor
CPU speed: 497.55 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE

Although I am very happy with a Celeron D I have in another machine (great overclocker), this reported downgrade of my laptop is quite worrying because most Celerons are lame.

Primenet stats now count the machine under the "celeron" heading too.

I ran CPU-Z to make sure I wasn't going crazy and was relieved to see it report:
Intel Pentium III E (Coppermine), brand id 2, 0.18u technology.
Family 6 model 8 stepping 1 revision cA2.

Memtest 86 agrees with me, it's still a Pentium 3 fortunately.

What I have discovered may be a bug in the 24.6 processor detection algorithm.
I understand why you would be changing processor detection to make the Athlons run optimised code, but perhaps in doing so, the existing detection has been broken.

Please could this be fixed so my machine is reclassified back to a Celeron, because I need to look after my credibility you know!

While you're working on that you might take the opportunity to include some recent cpu types eg why not determine and report Northwood or Prescott; and how about Celeron D as opposed to just classifying D as Celeron. I know the code does not fully query the processor just its capabilities and cache size, but I think you could differentiate these simply by establishing whether the processor could run SSE3 instructions. One reason to do this would be for benchmark comparisons - a Northwood and Prescott P4 machine speed result is only comparable if you know which chip you have inside, regardless of MHz/GHz. By the way, the improvement to AMD benchmarks is impressive.

Kind regards, Peter

XP 3200 results
 

George says these are slow so any experience on tweaking my PC greatly appreciated! I did originally via the bios have TURBO enabled and it was only after using Prime that I found out this was causing errors.

Phil

Here is the before and after. It is now looking very fast!?

[B]Before:[/B]

AMD Athlon(tm) XP 3200+
CPU speed: 2191.24 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
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: 256
Prime95 version 23.8, RdtscTiming=1
Best time for 384K FFT length: 53.340 ms.
Best time for 448K FFT length: 60.985 ms.
Best time for 512K FFT length: 65.846 ms.
Best time for 640K FFT length: 88.676 ms.
Best time for 768K FFT length: 105.773 ms.
Best time for 896K FFT length: 127.277 ms.
Best time for 1024K FFT length: 141.019 ms.
Best time for 1280K FFT length: 184.985 ms.
Best time for 1536K FFT length: 220.334 ms.
Best time for 1792K FFT length: 268.004 ms.
Best time for 2048K FFT length: 295.786 ms.
[Mon Jan 10 21:57:43 2005]
Compare your results to other computers at [url]http://www.mersenne.org/bench.htm[/url]
That web page also contains instructions on how your results can be
included.

[B]After:[/B]
AMD Athlon(tm) XP 3200+
CPU speed: 2191.11 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
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: 256
Prime95 version 24.6, RdtscTiming=1
Best time for 512K FFT length: 28.953 ms.
Best time for 640K FFT length: 39.764 ms.
Best time for 768K FFT length: 97.905 ms.
Best time for 896K FFT length: 119.919 ms.
Best time for 1024K FFT length: 133.308 ms.
Best time for 1280K FFT length: 171.875 ms.
Best time for 1536K FFT length: 206.033 ms.
Best time for 1792K FFT length: 123.722 ms.
Best time for 2048K FFT length: 279.577 ms.

[QUOTE=geoff]I came across this problem when I tried ECM on 10^311-1:

ECM found a factor in curve #1, stage #1
Sigma=7393313418913594, B1=110000000, B2=4290000000.
ERROR: Factor doesn't divide N!
10^311-1 completed 1 ECM curves, B1=110000000, B2=4290000000

I tried some smaller bounds and got mixed results, including one where the 'ERROR: Factor doesn't divide N!' message repeated over and over until I hit stop.[/QUOTE]

[QUOTE=Prime95]I'll look into the bug. BTW GMP-ECM should clean prime95's clock on this number.[/QUOTE]

Any progress on a fix for this :question:

I think that bug was fixed a while back. Let me know if the latest 24.6 still fails. If so, I can email a 24.9 to you.

[QUOTE=Prime95]I think that bug was fixed a while back. Let me know if the latest 24.6 still fails. If so, I can email a 24.9 to you.[/QUOTE]

Using the 14th Dec version of 24.6 I get this on 20^146 + 1 :-

ECM found a factor in curve #1, stage #1
Sigma=8212270044474278, B1=3000000, B2=300000000.
ERROR: Factor doesn't divide N!


On 80^101 - 1 Prime95 crashed with an unhandled exception. 0xC0000005 Access Violation.

Is it okay to run regular LL test now or what? =)

[QUOTE=phantom]Is it okay to run regular LL test now or what? =)[/QUOTE]

Yes. Dozens of successful double-checks have come in.

ahh good :), will start using it immediantly. Its way faster :)

Prime95 Plz where I can make download version 24.9 of Prime 95? :wink:

[QUOTE=renuac]Prime95 Plz where I can make download version 24.9 of Prime 95? :wink:[/QUOTE]


If you read the whole thread (in detail) you should be able to deduce where it might be.

24.6 and 24.9 are substaintial the same., AFAIK

I have only emailed one copy of 24.9 to one user. It isn't QA'ed as much as I would like. There is nothing useful in it - other than the no-execute fix.

Ah all good if you will be able to order me in my email: [email]renuac@somewhere[/email] for me is good, if you it will not be able not if it worries!

Sorry Bad English :wink:

Why hasn't the links for downloading 23.8 been switched to download24.6? Also, have all these errors 24.6 has given just beeninconsequential? It seems some computers have gotten some funny results.

[QUOTE=dominicanpapi82]Why hasn't the links for downloading 23.8 been switched to download24.6? Also, have all these errors 24.6 has given just beeninconsequential? It seems some computers have gotten some funny results.[/QUOTE]

Basically, I'm lazy :grin:

It is not uncommon for perfectly good versions to languish in Beta for months on end. I doubt 24.6 will ever be an official release as I'm already up to 24.10 internally. You might wonder why version numbers are jumping so. It is because version 24 has been all about ripping the FFT code cleanly out of prime95 and expanding its functionality for SoB, PFGW, LLR, and other projects. Every time I change the interface between these programs and the new gwnum library I bump the version number.

Right now I'm in the midst of porting the FFT code to 64-bit Windows. The Opteron actually passed a torture test last week! And no, it isn't any faster than 32-bit mode. First step is to port the existing assembly code, second step is to make use of the extra SSE2 registers. But right now, I'm rewriting the trial factoring code - at least that code should benefit greatly from 64-bit instructions.

As to your second question, there have been a few minor bugs found in 24.6, but none that affected LL results.

Thanks George for the status update! Much appreciated :bow:

Thanks George :razz: ! Version 24.10 already this finished?

My Results after 7 hours.
 

AMD Athlon XP-M
CPU speed: 2204.87 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
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: 256
Prime95 version 24.6, RdtscTiming=1
Best time for 512K FFT length: 29.067 ms.
Best time for 640K FFT length: 39.908 ms.
Best time for 768K FFT length: 48.696 ms.
Best time for 896K FFT length: 59.261 ms.
Best time for 1024K FFT length: 65.797 ms.
Best time for 1280K FFT length: 84.955 ms.
Best time for 1536K FFT length: 103.051 ms.
Best time for 1792K FFT length: 124.753 ms.
Best time for 2048K FFT length: 138.413 ms.
[Thu Jan 27 00:05:12 2005]
Self-test 1024K passed!
[Thu Jan 27 00:21:47 2005]
Self-test 8K passed!
[Thu Jan 27 00:37:21 2005]
Self-test 10K passed!
[Thu Jan 27 00:54:04 2005]
Self-test 896K passed!
[Thu Jan 27 01:10:20 2005]
Self-test 768K passed!
[Thu Jan 27 01:25:43 2005]
Self-test 12K passed!
[Thu Jan 27 01:41:04 2005]
Self-test 14K passed!
[Thu Jan 27 01:57:30 2005]
Self-test 640K passed!
[Thu Jan 27 02:16:25 2005]
Self-test 512K passed!
[Thu Jan 27 02:31:32 2005]
Self-test 16K passed!
[Thu Jan 27 02:47:09 2005]
Self-test 20K passed!
[Thu Jan 27 03:02:22 2005]
Self-test 448K passed!
[Thu Jan 27 03:17:42 2005]
Self-test 384K passed!
[Thu Jan 27 03:36:44 2005]
Self-test 24K passed!
[Thu Jan 27 03:52:05 2005]
Self-test 28K passed!
[Thu Jan 27 04:07:09 2005]
Self-test 320K passed!
[Thu Jan 27 04:22:30 2005]
Self-test 256K passed!
[Thu Jan 27 04:41:50 2005]
Self-test 32K passed!
[Thu Jan 27 04:56:55 2005]
Self-test 40K passed!
[Thu Jan 27 05:19:40 2005]
Self-test 224K passed!
[Thu Jan 27 05:35:28 2005]
Self-test 192K passed!
[Thu Jan 27 06:23:44 2005]
Self-test 48K passed!
[Thu Jan 27 06:39:52 2005]
Self-test 56K passed!
[Thu Jan 27 06:55:01 2005]
Self-test 160K passed!
[Thu Jan 27 07:13:58 2005]
Self-test 128K passed!
[Thu Jan 27 07:29:37 2005]
Self-test 64K passed!
[Thu Jan 27 07:35:04 2005]
FATAL ERROR: Final result was E79462C3, expected: 455509CD.
Hardware failure detected, consult stress.txt file.

AMD Athlon XP-M
CPU speed: 2260.21 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
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: 256
Prime95 version 24.6, RdtscTiming=1
Best time for 512K FFT length: 28.463 ms.
Best time for 640K FFT length: 39.035 ms.
Best time for 768K FFT length: 47.609 ms.
Best time for 896K FFT length: 57.863 ms.
Best time for 1024K FFT length: 64.360 ms.
Best time for 1280K FFT length: 83.233 ms.
Best time for 1536K FFT length: 100.096 ms.
Best time for 1792K FFT length: 122.372 ms.
Best time for 2048K FFT length: 136.048 ms.

I'm sure u know but..I failed big time under version 23.x..
But with 24.6..i pass for hours

I was going to even replace my whole system because I was failing..
Good thing I only sold my motherboard..Lol

[QUOTE=Prime95]
Right now I'm in the midst of porting the FFT code to 64-bit Windows. The Opteron actually passed a torture test last week! And no, it isn't any faster than 32-bit mode. First step is to port the existing assembly code, second step is to make use of the extra SSE2 registers. But right now, I'm rewriting the trial factoring code - at least that code should benefit greatly from 64-bit instructions.[/QUOTE]

Great to hear that the 64 bit development is progressing along with all the work that's been going into gwnum/FFT work.

Let me know if you need any test / double check runs on Athlon64s --
I have Server 2003 x64 and XP x64 machines eager to contribute their
XMM8 through XMM15 to the QA cause :smile:

Ethan O'Connor

I have an older Athlon system (850 Mhz) running a LL test that I would like to load the new 24.6 version on.

I assume it is OK to stop the V23.8 test, backup the entire Prime95 folder (just to be safe), copy the new Prime95.exe over the top of the old exe file, run some torture tests, and if no errors then let the new version take over the LL test right where the old version left off?

-Phil

I can confirm I´ve done that without any problems (confirmed DC...). As the save files are compatible with both versions that was expected, anyway.

Benches from a ThinkPad T42p.
This has the new 90nm Dothan 2.1GHz CPU with 2048K cache.
Having the CPUSupportsSSE2=0 in local.ini is the way to go (see last benchmark).

[B]v23.8[/B]
Intel(R) Pentium(R) M processor 2.10GHz
CPU speed: 598.09 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE, SSE2
L1 cache size: 32 KB
L2 cache size: unknown
L1 cache line size: 64 bytes
L2 cache line size: unknown
TLBS: 128
Prime95 version 23.8, RdtscTiming=1
Best time for 384K FFT length: 27.720 ms.
Best time for 448K FFT length: 33.687 ms.
Best time for 512K FFT length: 38.339 ms.
Best time for 640K FFT length: 47.494 ms.
Best time for 768K FFT length: 58.637 ms.
Best time for 896K FFT length: 70.227 ms.
Best time for 1024K FFT length: 79.036 ms.
Best time for 1280K FFT length: 101.587 ms.
Best time for 1536K FFT length: 124.214 ms.
Best time for 1792K FFT length: 148.483 ms.
Best time for 2048K FFT length: 166.576 ms.
Best time for 2560K FFT length: 216.207 ms.
Best time for 3072K FFT length: 265.680 ms.
Best time for 3584K FFT length: 316.736 ms.
Best time for 4096K FFT length: 354.189 ms.

[B]v24.6[/B]
Intel(R) Pentium(R) M processor 2.10GHz
CPU speed: 598.02 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE, SSE2
L1 cache size: 32 KB
L2 cache size: 2048 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
TLBS: 128
Prime95 version 24.6, RdtscTiming=1
Best time for 384K FFT length: 27.649 ms.
Best time for 448K FFT length: 34.016 ms.
Best time for 512K FFT length: 38.267 ms.
Best time for 640K FFT length: 47.619 ms.
Best time for 768K FFT length: 58.680 ms.
Best time for 896K FFT length: 70.195 ms.
Best time for 1024K FFT length: 79.536 ms.
Best time for 1280K FFT length: 101.980 ms.
Best time for 1536K FFT length: 124.214 ms.
Best time for 1792K FFT length: 148.658 ms.
Best time for 2048K FFT length: 166.922 ms.
Best time for 2560K FFT length: 216.495 ms.
Best time for 3072K FFT length: 264.464 ms.
Best time for 3584K FFT length: 316.664 ms.
Best time for 4096K FFT length: 354.836 ms.

[B]v24.6 with CPUSupportsSSE2=0[/B]
Intel(R) Pentium(R) M processor 2.10GHz
CPU speed: 598.03 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE
L1 cache size: 32 KB
L2 cache size: 2048 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
TLBS: 128
Prime95 version 24.6, RdtscTiming=1
Best time for 384K FFT length: 22.779 ms.
Best time for 448K FFT length: 27.817 ms.
Best time for 512K FFT length: 30.744 ms.
Best time for 640K FFT length: 41.254 ms.
Best time for 768K FFT length: 49.655 ms.
Best time for 896K FFT length: 60.458 ms.
Best time for 1024K FFT length: 66.971 ms.
Best time for 1280K FFT length: 87.029 ms.
Best time for 1536K FFT length: 107.687 ms.
Best time for 1792K FFT length: 131.243 ms.
Best time for 2048K FFT length: 145.665 ms.
Best time for 2560K FFT length: 190.889 ms.
Best time for 3072K FFT length: 227.660 ms.
Best time for 3584K FFT length: 278.245 ms.
Best time for 4096K FFT length: 308.510 ms.

What about a WinNT (without GUI) version of Prime95 24.6?

Is there going to be a link posted in the "Latest Version" thread?

Errrr... a bug?
 

hi,

try to "test" M127.

On 3 machines I have got
[code]
Iteration: 2/127, ERROR: Shift counter corrupt.
Possible hardware failure, consult the readme.txt file.
[/code]

I know 2^127-1 is rather small, but the message is confusing, and shouldn't be such that.

There was everything OK with M127 in version 23.8.

BTW: Stress test is going OK for many hours.

I get M127 is prime! WZ1: 00FE00FE
EDIT: This is using v23.4.1. What version are you using?
Oops, sorry. The name of this thread is 24.6. No further comments.

Re: Errr... a bug?
 

Hmmm...

Nobody can confirm the bug with testing "small" exponents in windows version of 24.6.1?

TO be exact: testing exponents below 350 (for example 349) gives a "shift counter corrupt" error.

Testing M7 (which worked in 23.8!) gives total crash of the program.

It's probably very stupid bug somewhere...

so please find and destroy ;-)

:squash: