![]() |
|
|
#144 |
|
"Mark"
Apr 2003
Between here and the
2×32×353 Posts |
The Mac version has been posted and hopefully the Linux can be posted in a few hours. This has been hampered by an upgrade to sourceforge the requires me and Steven Harvey (my Linux builder) to check everything out again.
|
|
|
|
|
|
#145 | |
|
Feb 2011
1416 Posts |
Quote:
Can't unpack using TotalCMD 8, now 7-zip, nor WinRAR 4.20. EDIT: What switch would you reccomend if I would like to test low ns Genefer with high b values (<100M range)? We have been doing on this back in 2009 but it may have changed since then... Last fiddled with by Honza on 2013-01-06 at 16:43 |
|
|
|
|
|
|
#146 | |
|
"Mark"
Apr 2003
Between here and the
2×32×353 Posts |
Quote:
I believe that -gx is what your looking for. |
|
|
|
|
|
|
#147 |
|
Feb 2005
Bristol, CT
33×19 Posts |
In the Windows zip file the 64 bit version is corrupt. The 32 bit version seems to work just fine.
|
|
|
|
|
|
#148 |
|
Dec 2011
After milion nines:)
145110 Posts |
Also on Boinc Confederation PFGW is not 3.7.0 as reported, but old one , since it is in byte same as version of pfgw in prp522 package
And I also try several times to download from sourceforge , but archive is invalid :( |
|
|
|
|
|
#149 | |
|
Dec 2011
After milion nines:)
1,451 Posts |
Quote:
64 bit LLR was always much faster then 64 bit PFGW 32 bit LLR was +/-small fraction of time same as 32 bit PFGW Both are tested on 64 bit Windows 7 So if I understand correctly on 32 bit host PFGW is faster from what program ( llr )? Thanks for reply! P.S PFGW32 bit 3.7.0 can be extracted from archive in sourceforge, and as stated above, works fine. PFGW64 bit 3.7.0 is broken :( ( please fix it) Last fiddled with by pepi37 on 2013-01-07 at 02:22 |
|
|
|
|
|
|
#150 | |
|
"Mark"
Apr 2003
Between here and the
11000110100102 Posts |
Quote:
If you are referring to base 2, then llr is much faster. I have heard similar claims for other bases, but I haven't compared them myself. Even if llr is faster for other bases, I would prefer to leave pfgw alone. The simple reason is that pfgw and llr perform a different test for primality. This allows one to use the both verify primality. (Changing the primality proving code of pfgw would be very hard as the code is fairly generic, i.e. it is not only use for k*b^n+/-1 but other forms as well.) Last fiddled with by rogue on 2013-01-07 at 03:30 |
|
|
|
|
|
|
#151 | |||
|
Feb 2011
22×5 Posts |
Quote:
It can differ more depending on CPU/cache/AVX/64-bit version and tested numbers/formats. ____ I've conducted a small test with GFN32768 and Genefer80, LLR64, PFGW64/AVX on i5-3570. All 4 apps where run at once. Quote:
Quote:
|
|||
|
|
|
|
|
#152 | ||
|
Dec 2011
After milion nines:)
1,451 Posts |
But I only use PFGW for LLR searching, not for Genefer, and in that case PFGW is about 10% slower , and even more, and when you calculate hundreds of results , and every result is calculating about hour, difference is noticeable :)
Quote:
Quote:
So 27 seconds compared to 30 seconds, and 55 seconds compared to 63 seconds are far away from only 1% of difference :) |
||
|
|
|
|
|
#153 | |
|
Feb 2011
22×5 Posts |
I'm glad you found what suites you and your hardware.
As I stated before, it depends on several factors like CPU, tests done, single or on all cores etc. Intel i7-3820, 32GB RAM, LLR64 and PFGW gives same runtime when only single instance. Quote:
|
|
|
|
|
|
|
#154 |
|
Dec 2011
After milion nines:)
5AB16 Posts |
Yes, it looks like it is CPU dependent. Thanks for point this thing up Honza.
|
|
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| A possible bug in LLR/PFGW while using GWNUM (no bug in P95) | Batalov | Software | 77 | 2015-04-14 09:01 |
| PFGW 3.2.0 has been Released | rogue | Software | 94 | 2010-09-14 21:39 |
| PFGW 3.2.3 has been Released | rogue | Software | 10 | 2009-10-28 07:07 |
| PFGW 3.2.2 has been Released | rogue | Software | 20 | 2009-08-23 12:14 |
| PFGW 3.2.1 has been released | rogue | Software | 5 | 2009-08-10 01:43 |