Early Beta of version 24.11 - Page 9

Mike · 2005-05-03, 01:43

Intel(R) Pentium(R) 4 CPU 2.60GHz
CPU speed: 2612.57 MHz
CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE, SSE2
L1 cache size: 8 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 128 bytes
TLBS: 64
Prime95 version 23.8, RdtscTiming=1
Best time for 384K FFT length: 13.807 ms.
Best time for 448K FFT length: 16.536 ms.
Best time for 512K FFT length: 18.868 ms.
Best time for 640K FFT length: 22.671 ms.
Best time for 768K FFT length: 27.598 ms.
Best time for 896K FFT length: 32.743 ms.
Best time for 1024K FFT length: 36.528 ms.
Best time for 1280K FFT length: 47.860 ms.
Best time for 1536K FFT length: 59.169 ms.
Best time for 1792K FFT length: 70.219 ms.
Best time for 2048K FFT length: 79.702 ms.

Intel(R) Pentium(R) 4 CPU 2.60GHz
CPU speed: 2612.51 MHz
CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2
L1 cache size: 8 KB
L2 cache size: 512 KB
L1 cache line size: 64 bytes
L2 cache line size: 128 bytes
TLBS: 64
Prime95 version 24.11, RdtscTiming=1
Best time for 512K FFT length: 18.406 ms.
Best time for 640K FFT length: 22.227 ms.
Best time for 768K FFT length: 27.372 ms.
Best time for 896K FFT length: 32.520 ms.
Best time for 1024K FFT length: 36.297 ms.
Best time for 1280K FFT length: 47.394 ms.
Best time for 1536K FFT length: 59.044 ms.
Best time for 1792K FFT length: 69.496 ms.
Best time for 2048K FFT length: 78.504 ms.
Best time for 58 bit trial factors: 11.232 ms.
Best time for 59 bit trial factors: 11.281 ms.
Best time for 60 bit trial factors: 11.224 ms.
Best time for 61 bit trial factors: 11.291 ms.
Best time for 62 bit trial factors: 12.231 ms.
Best time for 63 bit trial factors: 12.195 ms.
Best time for 64 bit trial factors: 14.845 ms.
Best time for 65 bit trial factors: 14.821 ms.
Best time for 66 bit trial factors: 14.797 ms.
Best time for 67 bit trial factors: 14.754 ms.

My P4 loves 24.11!

moo · 2005-05-03, 03:17

give benchmarks for other versions.... mike

dave_0273 · 2005-05-03, 11:27

Quote:

Originally Posted by moo

give benchmarks for other versions.... mike

Mike has already posteded benchmarks for 2 different versions of prime95. However, he isn't really getting a speed boost because (i am assuming) that his P4 is 32bit, and 24.11 only gave a speed boost to 64 bit chips.

Can someone please correct me if I am wrong?

Quote:

Originally Posted by Mike

My P4 loves 24.11!

I am a little confused. I don't see a significant speed boost... is there another reason why you like it over 23.8 or am I just reading the numbers wrong?

Mike · 2005-05-03, 12:44

The difference isn't significant, but version 24 is a TAD faster.

Best time for 512K FFT length: 18.868 ms. vs. 18.406 ms. (0.462 ms better.)
Best time for 1024K FFT length: 36.528 ms. vs. 36.297 ms. (0.231 ms better.)
Best time for 2048K FFT length: 79.702 ms. vs. 78.504 ms. (1.198 ms better.)

I'll take whatever advantage, however slight it is.

Joe O · 2005-05-03, 12:51

Starting with 512K FFT length and finishing with 2048K FFT length he has shown the following improvements:

2.51%
2.00%
0.83%
0.69%
0.64%
0.98%
0.21%
1.04%
1.53%

Peter Nelson · 2005-05-03, 14:20

1. The last FIVE posts would have been better placed under the so-called "perpetual benchmark thread".

2. You will see for example, I ran the new 24.11 client on a 630 machine and posted there not here.

3. If you are running/benchmarking this beta client please say EXACTLY what version of 24.11 you have (ie by date downloaded from the ftp server or subversion number) since it has been through at least FOUR updates already.

4. Yes, the improvement on P4 is only slight but it is a little faster which I welcome.

5. I like 24.11 because of the ability to benchmark trial factoring.

6. I also like it because of the massive performance jump if you are running in 64 bit mode (eg Athlon64 with 64 bit windows beta).

7. I hope that not too long in the future, we can get this for 64-bit Linux eg on Athlon64 or Intel 6xx / 8xx with EM64T.

8. My own opinion is that this thread is best left for feedback of experiences with the beta like bug reports, testing queries etc.

Dresdenboy · 2005-05-03, 15:11

I asked on the Aceshardware forum, if someone could test Prime95 21.11 on an EM64T CPU with 64 bit OS. And got results

Quote:

Originally Posted by Kevin Sheppard

3.0 Ghz Nocona's running CTP 2 (1433).

64 bit.

Code:

[Tue May 03 15:48:51 2005]
Compare your results to other computers at http://www.mersenne.org/bench.htm
That web page also contains instructions on how your results can be included.

Intel(R) Xeon(TM) CPU 3.00GHz
CPU speed: 2992.96 MHz
CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2
L1 cache size: 16 KB
L2 cache size: 1024 KB
L1 cache line size: 64 bytes
L2 cache line size: 128 bytes
TLBS: 64
Prime95 version 24.11, RdtscTiming=1
Best time for 512K FFT length: 18.243 ms.
Best time for 640K FFT length: 21.581 ms.
Best time for 768K FFT length: 26.084 ms.
Best time for 896K FFT length: 31.616 ms.
Best time for 1024K FFT length: 35.122 ms.
Best time for 1280K FFT length: 45.999 ms.
Best time for 1536K FFT length: 55.608 ms.
Best time for 1792K FFT length: 67.340 ms.
Best time for 2048K FFT length: 75.183 ms.
Best time for 58 bit trial factors: 8.183 ms.
Best time for 59 bit trial factors: 8.164 ms.
Best time for 60 bit trial factors: 8.472 ms.
Best time for 61 bit trial factors: 8.775 ms.
Best time for 62 bit trial factors: 11.129 ms.
Best time for 63 bit trial factors: 13.693 ms.
Best time for 64 bit trial factors: 15.448 ms.
Best time for 65 bit trial factors: 17.129 ms.
Best time for 66 bit trial factors: 16.990 ms.
Best time for 67 bit trial factors: 16.923 ms.

32bit.

Code:

[Tue May 03 15:49:40 2005]
Compare your results to other computers at http://www.mersenne.org/bench.htm
That web page also contains instructions on how your results can be included.

Intel(R) Xeon(TM) CPU 3.00GHz
CPU speed: 2992.76 MHz
CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2
L1 cache size: 16 KB
L2 cache size: 1024 KB
L1 cache line size: 64 bytes
L2 cache line size: 128 bytes
TLBS: 64
Prime95 version 24.11, RdtscTiming=1
Best time for 512K FFT length: 18.239 ms.
Best time for 640K FFT length: 21.563 ms.
Best time for 768K FFT length: 26.156 ms.
Best time for 896K FFT length: 31.685 ms.
Best time for 1024K FFT length: 35.210 ms.
Best time for 1280K FFT length: 46.194 ms.
Best time for 1536K FFT length: 55.848 ms.
Best time for 1792K FFT length: 67.308 ms.
Best time for 2048K FFT length: 75.251 ms.
Best time for 58 bit trial factors: 9.176 ms.
Best time for 59 bit trial factors: 9.214 ms.
Best time for 60 bit trial factors: 9.108 ms.
Best time for 61 bit trial factors: 9.139 ms.
Best time for 62 bit trial factors: 12.831 ms.
Best time for 63 bit trial factors: 12.847 ms.
Best time for 64 bit trial factors: 14.657 ms.
Best time for 65 bit trial factors: 14.765 ms.
Best time for 66 bit trial factors: 14.673 ms.
Best time for 67 bit trial factors: 14.828 ms.

Link: Original posting

I made a table comparing the TF results:

Code:

                                     32 bit       64 bit
Best time for 58 bit trial factors:  9.176 ms.    8.183 ms
Best time for 59 bit trial factors:  9.214 ms.    8.164 ms
Best time for 60 bit trial factors:  9.108 ms.    8.472 ms
Best time for 61 bit trial factors:  9.139 ms.    8.775 ms
Best time for 62 bit trial factors: 12.831 ms.   11.129 ms
Best time for 63 bit trial factors: 12.847 ms.   13.693 ms
Best time for 64 bit trial factors: 14.657 ms.   15.448 ms
Best time for 65 bit trial factors: 14.765 ms.   17.129 ms
Best time for 66 bit trial factors: 14.673 ms.   16.990 ms
Best time for 67 bit trial factors: 14.828 ms.   16.923 ms

Peter Nelson · 2005-05-05, 01:45

Just an idea, but now that a 64 bit version exists, from the number of benchmarks getting posted it is not always immediately obvious whether the machine is running in 32 or 64 bit mode.

When the benchmark prints out version number, processor speed etc could it possibly also display 32bit or 64bit which should be readily available to the client as they are distinct executables.

This will standardise where to find this info in a benchmark and save people having to say or ask which it is.

penguin22 · 2005-05-10, 20:21

Hello,

I'm dual booting now with Windows XP Pro and XP Pro x64 Edition and would like to use the same data files to work on the same numbers between boots. Is this supported with this new version of Prime95 24.11? And if so what would be the best practice.

I have a common drive M that stays the same on both boots, but the C & D drive swap depending what OS I'm in. This shouldn't be a problem though I wouldn't think as long as I can direct the Prime95 clients to work from the data located on the M drive (if I can do that).

Any help would be greatly appreciated. Thanks!

Uncwilly · 2005-05-10, 21:05

Install Prime95 to your M and it all should be fine. After swaping to the other operating system, manually start Prime again and it should then start again no problem.

penguin22 · 2005-05-10, 21:45

Thanks for the quick reply, but the problem is that I want to use the 32bit version of Prime95 on the 32bit OS and the 64bit version under the 64bit OS...

Problem being that they have the same exe name and you can't have them both under the same directory. It's one or the other, not both.

2005-05-05, 01:45	#96
Peter Nelson Oct 2004 23² Posts	Please display 32 or 64 bit for benchmarking Just an idea, but now that a 64 bit version exists, from the number of benchmarks getting posted it is not always immediately obvious whether the machine is running in 32 or 64 bit mode. When the benchmark prints out version number, processor speed etc could it possibly also display 32bit or 64bit which should be readily available to the client as they are distinct executables. This will standardise where to find this info in a benchmark and save people having to say or ask which it is.

2005-05-10, 20:21	#97
penguin22 Sep 2002 2²·3 Posts	Dual Booting with both new 24.11's Hello, I'm dual booting now with Windows XP Pro and XP Pro x64 Edition and would like to use the same data files to work on the same numbers between boots. Is this supported with this new version of Prime95 24.11? And if so what would be the best practice. I have a common drive M that stays the same on both boots, but the C & D drive swap depending what OS I'm in. This shouldn't be a problem though I wouldn't think as long as I can direct the Prime95 clients to work from the data located on the M drive (if I can do that). Any help would be greatly appreciated. Thanks!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Prime95 beta version 28.4	Prime95	Software	20	2014-03-02 02:51
Prime95 beta version 28.3	Prime95	Software	68	2014-02-23 05:42
Prime95 version 27.1 early preview, not-even-close-to-beta release	Prime95	Software	126	2012-02-09 16:17
Beta version 24.12 available	Prime95	Software	33	2005-06-14 13:19
Beta version of PRP	Prime95	PSearch	15	2004-09-17 19:21

2005-05-03, 01:43	#89
Mike May 2004 Vancouver, Canada 2²×5² Posts	Intel(R) Pentium(R) 4 CPU 2.60GHz CPU speed: 2612.57 MHz CPU features: RDTSC, CMOV, PREFETCH, MMX, SSE, SSE2 L1 cache size: 8 KB L2 cache size: 512 KB L1 cache line size: 64 bytes L2 cache line size: 128 bytes TLBS: 64 Prime95 version 23.8, RdtscTiming=1 Best time for 384K FFT length: 13.807 ms. Best time for 448K FFT length: 16.536 ms. Best time for 512K FFT length: 18.868 ms. Best time for 640K FFT length: 22.671 ms. Best time for 768K FFT length: 27.598 ms. Best time for 896K FFT length: 32.743 ms. Best time for 1024K FFT length: 36.528 ms. Best time for 1280K FFT length: 47.860 ms. Best time for 1536K FFT length: 59.169 ms. Best time for 1792K FFT length: 70.219 ms. Best time for 2048K FFT length: 79.702 ms. Intel(R) Pentium(R) 4 CPU 2.60GHz CPU speed: 2612.51 MHz CPU features: RDTSC, CMOV, Prefetch, MMX, SSE, SSE2 L1 cache size: 8 KB L2 cache size: 512 KB L1 cache line size: 64 bytes L2 cache line size: 128 bytes TLBS: 64 Prime95 version 24.11, RdtscTiming=1 Best time for 512K FFT length: 18.406 ms. Best time for 640K FFT length: 22.227 ms. Best time for 768K FFT length: 27.372 ms. Best time for 896K FFT length: 32.520 ms. Best time for 1024K FFT length: 36.297 ms. Best time for 1280K FFT length: 47.394 ms. Best time for 1536K FFT length: 59.044 ms. Best time for 1792K FFT length: 69.496 ms. Best time for 2048K FFT length: 78.504 ms. Best time for 58 bit trial factors: 11.232 ms. Best time for 59 bit trial factors: 11.281 ms. Best time for 60 bit trial factors: 11.224 ms. Best time for 61 bit trial factors: 11.291 ms. Best time for 62 bit trial factors: 12.231 ms. Best time for 63 bit trial factors: 12.195 ms. Best time for 64 bit trial factors: 14.845 ms. Best time for 65 bit trial factors: 14.821 ms. Best time for 66 bit trial factors: 14.797 ms. Best time for 67 bit trial factors: 14.754 ms. My P4 loves 24.11!

2005-05-03, 03:17	#90
moo Jul 2004 Nowhere 809 Posts	give benchmarks for other versions.... mike

2005-05-03, 12:44	#92
Mike May 2004 Vancouver, Canada 2²·5² Posts	The difference isn't significant, but version 24 is a TAD faster. Best time for 512K FFT length: 18.868 ms. vs. 18.406 ms. (0.462 ms better.) Best time for 1024K FFT length: 36.528 ms. vs. 36.297 ms. (0.231 ms better.) Best time for 2048K FFT length: 79.702 ms. vs. 78.504 ms. (1.198 ms better.) I'll take whatever advantage, however slight it is.

2005-05-03, 12:51	#93
Joe O Aug 2002 525₁₀ Posts	Starting with 512K FFT length and finishing with 2048K FFT length he has shown the following improvements: 2.51% 2.00% 0.83% 0.69% 0.64% 0.98% 0.21% 1.04% 1.53%

2005-05-03, 14:20	#94
Peter Nelson Oct 2004 23² Posts	1. The last FIVE posts would have been better placed under the so-called "perpetual benchmark thread". 2. You will see for example, I ran the new 24.11 client on a 630 machine and posted there not here. 3. If you are running/benchmarking this beta client please say EXACTLY what version of 24.11 you have (ie by date downloaded from the ftp server or subversion number) since it has been through at least FOUR updates already. 4. Yes, the improvement on P4 is only slight but it is a little faster which I welcome. 5. I like 24.11 because of the ability to benchmark trial factoring. 6. I also like it because of the massive performance jump if you are running in 64 bit mode (eg Athlon64 with 64 bit windows beta). 7. I hope that not too long in the future, we can get this for 64-bit Linux eg on Athlon64 or Intel 6xx / 8xx with EM64T. 8. My own opinion is that this thread is best left for feedback of experiences with the beta like bug reports, testing queries etc.

2005-05-10, 21:05	#98
Uncwilly 6809 > 6502 """"""""""""""""""" Aug 2003 101×103 Posts 22237₈ Posts	Install Prime95 to your M and it all should be fine. After swaping to the other operating system, manually start Prime again and it should then start again no problem.

2005-05-10, 21:45	#99
penguin22 Sep 2002 2²·3 Posts	Thanks for the quick reply, but the problem is that I want to use the 32bit version of Prime95 on the 32bit OS and the 64bit version under the 64bit OS... Problem being that they have the same exe name and you can't have them both under the same directory. It's one or the other, not both.