mersenneforum.org  

Go Back   mersenneforum.org > Great Internet Mersenne Prime Search > Software

Reply
 
Thread Tools
Old 2005-04-05, 21:19   #23
moo
 
moo's Avatar
 
Jul 2004
Nowhere

11001010012 Posts
Default

d00d
moo is offline   Reply With Quote
Old 2005-04-06, 15:21   #24
typo_pl
 
Apr 2005

410 Posts
Default

I guess I'm the first to download the source code/complain about the source code URL.

Here's a working URL, notice the misplaced 'r':
ftp://mersenne.org/gimps/srouce24.zip

George: Filename now fixed on the server

Last fiddled with by Prime95 on 2005-04-06 at 15:38
typo_pl is offline   Reply With Quote
Old 2005-04-06, 18:11   #25
Washuu
 
Mar 2005
Poland

2·17 Posts
Thumbs down Another ProxyServer request...

I have troubles connecting to Primenet. So i started reading all threads about it... and investigating.

Now I know: my proxy server (to which I have no access... ) is configured in that way, so it accepts request

GET http://mersenne.org/cgi-bin/pnHttp.exe?(...)

but DOES NOT

GET http://mersenne.org:80/cgi-bin/pnHttp.exe?(...)

which is used by prime95 communication.

Is there any switch I can use? Or may I put a request for such?


BTW: there was PrimeNet 4.0 Proxy Server some years ago... Pity that it isn't developed more...
Washuu is offline   Reply With Quote
Old 2005-04-06, 23:42   #26
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

7×1,019 Posts
Default

There is no switch you can use. I'll put in a fix for the next 24.11 update.
Prime95 is offline   Reply With Quote
Old 2005-04-07, 10:26   #27
sharad
 
Jul 2004
Aotearoa

23 Posts
Thumbs up

Using...

ftp://mersenne.org/gimps/p95v2411.zip:
AMD Athlon(tm) 64 Processor 3000+
CPU speed: 1809.21 MHz
Windows XP Pro. (32bit)

Code:
Prime95 version 24.6, RdtscTiming=1
Best time for 512K FFT length: 32.254 ms.
Best time for 640K FFT length: 40.449 ms.
Best time for 768K FFT length: 49.186 ms.
Best time for 896K FFT length: 59.303 ms.
Best time for 1024K FFT length: 66.494 ms.
Best time for 1280K FFT length: 88.572 ms.
Best time for 1536K FFT length: 106.560 ms.
Best time for 1792K FFT length: 128.943 ms.
Best time for 2048K FFT length: 148.450 ms.

Prime95 version 24.11, RdtscTiming=1
Best time for 512K FFT length: 30.152 ms.
Best time for 640K FFT length: 37.092 ms.
Best time for 768K FFT length: 44.866 ms.
Best time for 896K FFT length: 54.281 ms.
Best time for 1024K FFT length: 60.341 ms.
Best time for 1280K FFT length: 80.006 ms.
Best time for 1536K FFT length: 97.621 ms.
Best time for 1792K FFT length: 117.558 ms.
Best time for 2048K FFT length: 130.864 ms.
Nice boost but is it ok to switch to the new version if you are in between a factoring assignment?
sharad is offline   Reply With Quote
Old 2005-04-07, 15:11   #28
SalemTheCat100
 
Oct 2002

2·13 Posts
Default Athlon 3400+ @2.5ghz timings

Running on Windows XP 64bit Build 1433

AMD Athlon(tm) 64 Processor 3400+ overclocked 4%
1gb PC3200 Crucial DDR 3-3-3-8
CPU speed: 2495.91 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 23.8, RdtscTiming=1
Best time for 512K FFT length: 25.650 ms.
Best time for 640K FFT length: 32.008 ms.
Best time for 768K FFT length: 38.921 ms.
Best time for 896K FFT length: 46.940 ms.
Best time for 1024K FFT length: 52.920 ms.
Best time for 1280K FFT length: 70.715 ms.
Best time for 1536K FFT length: 84.584 ms.
Best time for 1792K FFT length: 102.695 ms.
Best time for 2048K FFT length: 116.308 ms.

Prime95 version 24.6 with SSE2, RdtscTiming=1
Best time for 512K FFT length: 25.911 ms.
Best time for 640K FFT length: 32.005 ms.
Best time for 768K FFT length: 39.066 ms.
Best time for 896K FFT length: 47.263 ms.
Best time for 1024K FFT length: 53.246 ms.
Best time for 1280K FFT length: 71.135 ms.
Best time for 1536K FFT length: 84.945 ms.
Best time for 1792K FFT length: 103.066 ms.
Best time for 2048K FFT length: 117.047 ms.

Prime95 version 24.6 no SSE2, RdtscTiming=1
Best time for 512K FFT length: 24.035 ms.
Best time for 640K FFT length: 32.138 ms.
Best time for 768K FFT length: 38.689 ms.
Best time for 896K FFT length: 46.980 ms.
Best time for 1024K FFT length: 52.488 ms.
Best time for 1280K FFT length: 69.806 ms.
Best time for 1536K FFT length: 83.631 ms.
Best time for 1792K FFT length: 100.429 ms.
Best time for 2048K FFT length: 111.799 ms.

Prime95 version 24.11 32bit code, RdtscTiming=1
Best time for 512K FFT length: 23.132 ms.
Best time for 640K FFT length: 27.318 ms.
Best time for 768K FFT length: 33.018 ms.
Best time for 896K FFT length: 40.094 ms.
Best time for 1024K FFT length: 44.604 ms.
Best time for 1280K FFT length: 59.142 ms.
Best time for 1536K FFT length: 72.431 ms.
Best time for 1792K FFT length: 87.165 ms.
Best time for 2048K FFT length: 97.316 ms.

Best time for 58 bit trial factors: 4.852 ms.
Best time for 59 bit trial factors: 4.838 ms.
Best time for 60 bit trial factors: 4.818 ms.
Best time for 61 bit trial factors: 4.840 ms.
Best time for 62 bit trial factors: 8.809 ms.
Best time for 63 bit trial factors: 8.810 ms.
Best time for 64 bit trial factors: 11.193 ms.
Best time for 65 bit trial factors: 11.149 ms.
Best time for 66 bit trial factors: 11.132 ms.
Best time for 67 bit trial factors: 11.088 ms.

Prime95 version 24.11 64bit code, RdtscTiming=1
Best time for 512K FFT length: 23.093 ms.
Best time for 640K FFT length: 27.489 ms.
Best time for 768K FFT length: 33.122 ms.
Best time for 896K FFT length: 40.072 ms.
Best time for 1024K FFT length: 44.526 ms.
Best time for 1280K FFT length: 59.238 ms.
Best time for 1536K FFT length: 72.824 ms.
Best time for 1792K FFT length: 87.254 ms.
Best time for 2048K FFT length: 97.604 ms.

Best time for 58 bit trial factors: 3.037 ms.
Best time for 59 bit trial factors: 3.038 ms.
Best time for 60 bit trial factors: 3.238 ms.
Best time for 61 bit trial factors: 3.320 ms.
Best time for 62 bit trial factors: 3.893 ms.
Best time for 63 bit trial factors: 4.536 ms.
Best time for 64 bit trial factors: 5.480 ms.
Best time for 65 bit trial factors: 6.424 ms.
Best time for 66 bit trial factors: 6.388 ms.
Best time for 67 bit trial factors: 6.372 ms.

Nice work.

Salem
SalemTheCat100 is offline   Reply With Quote
Old 2005-04-08, 15:55   #29
Peter Nelson
 
Peter Nelson's Avatar
 
Oct 2004

232 Posts
Default Benchmark of Trial Factoring (Linux Client)

Quote:
Originally Posted by Prime95
Done. Look for it next time I upload an executable
George, thanks for the new factoring benchmark, it's very useful on my Windows XP machines.

For instance comparing Dresdenboy's A64 3000+ with my 3GHz P4, the P4 is still much faster at LL but they are about the same for TF in 32-bit. And in 64-bit, the A64 is significantly faster at TF work.

a)

Users of the TF benchmark stats should note that whilst then benchmark says eg 62 bit this is equivalent to what factoring runs call "to 2^63". And so on for each bit size. This is correct but could be potentially confusing. I wonder if the factoring could say FROM 2^62 TO 2^63 (for clarity), whereas the benchmark can stay as is.

b)

However I also downloaded the latest Linux (32-bit) version which identifies itself as 24.11.2. Upon execution I found the benchmark output only contains the LL not the factoring tests.

It's the statically linked one I tried because the dynamic linked one needs libstdc++.so.6 to run. (Suse 9.3 comes out in about a week so I will be reinstalling from it and don't want to mess about with libraries etc before then).

The mprime files on the ftp server have the linux as slightly newer than the Windows version.

Did you intend to recompile and make a newer linux client available from the latest source?
Or does the linux client not support benchmarking of factoring speed?
I assume it's the same source code for both platform so was confused why the linux build doesn't do it (yet). This would be nice for cross-platform comparisons.

Please explain any options I need to set to get the factor benchmark on static mprime, or provide a version which does it from the normal benchmark menu as I expected.

Thanks in anticipation, Peter

c)

P.S. Quite unrelated, but which version of MASM are you using to turn your assembly files into object code (I'm particularly interested in relation to understanding your 64-bit compilation environment).

Last fiddled with by Peter Nelson on 2005-04-08 at 16:03
Peter Nelson is offline   Reply With Quote
Old 2005-04-08, 20:18   #30
Prime95
P90 years forever!
 
Prime95's Avatar
 
Aug 2002
Yeehaw, FL

11011110111012 Posts
Default

Linux mprime should give you the factoring benchmark too. I probably made a mistake in building or uploading it.

My 64-bit build environment is MS Visual Studio 2005 a.k.a. Whidbey. It cost $10 for a time-limited beta version. I don't know what the final version will cost.

Masm for 32-bit is version 8.00.40607.16
Masm for 64-bit is also version 8.00.40607.16 but is a different executable.
Prime95 is offline   Reply With Quote
Old 2005-04-11, 05:49   #31
dans
 
dans's Avatar
 
Oct 2002

1516 Posts
Default SSE2 option under new version

Quote:
Originally Posted by Prime95
Time it both ways. I'm betting the SSE2 code is now faster for the same FFT size.
According to my benchmarks, don't use that option anymore!

Benchmark WITH the "CpuSupportsSSE2=0" option set
AMD Athlon(tm) 64 Processor 3200+
CPU speed: 1994.68 MHz
Prime95 version 24.11, RdtscTiming=1
Best time for 512K FFT length: 30.266 ms.
Best time for 640K FFT length: 40.544 ms.
Best time for 768K FFT length: 48.946 ms.
Best time for 896K FFT length: 59.808 ms.
Best time for 1024K FFT length: 66.461 ms.
Best time for 1280K FFT length: 87.620 ms.
Best time for 1536K FFT length: 107.221 ms.
Best time for 1792K FFT length: 126.338 ms.
Best time for 2048K FFT length: 140.388 ms.
Best time for 58 bit trial factors: 6.119 ms.
Best time for 59 bit trial factors: 6.107 ms.
Best time for 60 bit trial factors: 6.119 ms.
Best time for 61 bit trial factors: 6.110 ms.
Best time for 62 bit trial factors: 11.132 ms.
Best time for 63 bit trial factors: 11.108 ms.
Best time for 64 bit trial factors: 21.321 ms.
Best time for 65 bit trial factors: 21.928 ms.
Best time for 66 bit trial factors: 22.479 ms.
Best time for 67 bit trial factors: 22.696 ms.

Benchmark WITHOUT "CpuSupportsSSE2=0" option set
AMD Athlon(tm) 64 Processor 3200+
CPU speed: 1994.98 MHz
Prime95 version 24.11, RdtscTiming=1
Best time for 512K FFT length: 28.707 ms.
Best time for 640K FFT length: 67.948 ms.
Best time for 768K FFT length: 77.572 ms.
Best time for 896K FFT length: 50.826 ms.
Best time for 1024K FFT length: 56.583 ms.
Best time for 1280K FFT length: 74.948 ms.
Best time for 1536K FFT length: 91.276 ms.
Best time for 1792K FFT length: 109.248 ms.
Best time for 2048K FFT length: 122.294 ms.
Best time for 58 bit trial factors: 6.096 ms.
Best time for 59 bit trial factors: 6.111 ms.
Best time for 60 bit trial factors: 6.087 ms.
Best time for 61 bit trial factors: 6.109 ms.
Best time for 62 bit trial factors: 11.139 ms.
Best time for 63 bit trial factors: 11.112 ms.
Best time for 64 bit trial factors: 14.203 ms.
Best time for 65 bit trial factors: 14.278 ms.
Best time for 66 bit trial factors: 14.301 ms.
Best time for 67 bit trial factors: 14.138 ms.

Last fiddled with by dans on 2005-04-11 at 05:52
dans is offline   Reply With Quote
Old 2005-04-11, 10:43   #32
TheJudger
 
TheJudger's Avatar
 
"Oliver"
Mar 2005
Germany

110710 Posts
Default

Quote:
Originally Posted by Peter Nelson
However I also downloaded the latest Linux (32-bit) version which identifies itself as 24.11.2. Upon execution I found the benchmark output only contains the LL not the factoring tests.

It's the statically linked one I tried because the dynamic linked one needs libstdc++.so.6 to run. (Suse 9.3 comes out in about a week so I will be reinstalling from it and don't want to mess about with libraries etc before then).
On my SuSE 9.2 Systems a simple symbolic link helped...
Code:
cd /usr/lib/
ln -s libstdc++.so.5 libstdc++.so.6
Yeah, I know that's quick&dirty ;)
TheJudger is offline   Reply With Quote
Old 2005-04-11, 13:14   #33
Peter Nelson
 
Peter Nelson's Avatar
 
Oct 2004

21116 Posts
Default

Quote:
Originally Posted by TheJudger
On my SuSE 9.2 Systems a simple symbolic link helped...
Code:
cd /usr/lib/
ln -s libstdc++.so.5 libstdc++.so.6
Yeah, I know that's quick&dirty ;)
Thanks for the suggestion, that's one way around it, but the statically linked version runs for me so I don't need the dynamic one to find its external library. I will only need the library when I compile it all myself, and I won't be doing that before my 9.3 OS upgrade.

The reason I explained that it was the STATIC build version of mprime was to help George identify the problem (ie which file I had tried executing which exhibited my lack of factoring benchmark problem) and to explain that I was unable to state whether the same problem was present in the dynamic build.

As it turns out, it probably was a simple oversight with his build procedure meaning that the ftp file didn't reflect his latest source.

I'm waiting until he does a re-build and uploads a new static mprime containing the factoring benchmark. This may coincide with the next bugfix, and I was trying to be patient by not asking "Rebuild and upload it now".

Last fiddled with by Peter Nelson on 2005-04-11 at 13:16
Peter Nelson is offline   Reply With Quote
Reply

Thread Tools


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

All times are UTC. The time now is 13:50.

Wed Oct 21 13:50:37 UTC 2020 up 41 days, 11:01, 1 user, load averages: 1.34, 1.24, 1.42

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.