20201129, 01:52  #23 
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
5·953 Posts 

20201202, 02:25  #24 
Jun 2003
The Computer
611_{8} Posts 
I went ahead and took the liberty of reserving that exponent to 91 bits. It's a comparatively slow 100 days on my GTX 1080, but it will be good to have an exponent fully factored. I will check my local electronics store for a 3060 Ti tomorrow morning, which should give a faster ETA at an affordable price.

20201202, 02:33  #25 
Oct 2007
Manchester, UK
2^{4}×5×17 Posts 

20201203, 04:44  #26 
Jun 2003
The Computer
3·131 Posts 
Perhaps I should say fully factored...to the optimal 91 bit depth! A factor would at least avoid the arduous P1 and PRP tests, but those will also be an interesting challenge.
I was lucky enough to get a 3060 Ti this morning, despite there being over 100 people in a line that started forming the day before! I will install that and see what the new ETA is. 
20210216, 15:03  #27 
Jun 2003
The Computer
3×131 Posts 
It isn't reflecting on mersenne.ca yet, but I factored 3321928171 to 91 bits with no factor. Anyone with a Radeon VII Pro who is willing to crunch a P1 and PRP test is good to go!

20210216, 18:41  #28 
Oct 2007
Manchester, UK
2^{4}·5·17 Posts 
Now you can get to mining ETH with that thing.

20210218, 06:19  #29 
Jun 2003
The Computer
3×131 Posts 

20210826, 18:05  #30  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
1011010001100_{2} Posts 
Quote:
Code:
20210803 04:13:45 asr2/radeonvii2 990004423 P2(33M,990M) D=210, nBuf=21 20210803 08:38:46 GpuOwl VERSION v7.253ge27846f 20210803 08:38:46 config: user kriesel cpu asr2/radeonvii2 d 2 maxAlloc 14G proof 10 use NO_ASM autoverify 10 block 1000 autoverify 11 20210803 08:38:46 device 2, unique id '' 20210803 08:38:46 asr2/radeonvii2 990004423 FFT: 56M 4K:14:512 (16.86 bpw) The alternative is Mlucas v20.0 with its new P1 capability, which I'm looking into. Run times for P1 would be even longer, perhaps 48 months on a Xeon Phi 7250. Mlucas v20.0 or earlier does not have PRP proof generation yet. That's what Ernst plans to add next IIRC. PRP test run times would be very long (decades on my hardware). Last fiddled with by kriesel on 20210826 at 18:17 

20210929, 19:22  #31 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
1011010001100_{2} Posts 
That's the right place to stop for your GTX1080. RTX20xx, GTX16xx, RTX30xx, probably 92 bits. (Mfakto max 92 bits; Mfaktc 95 max)
Last fiddled with by kriesel on 20210929 at 19:23 
20211014, 03:09  #32  
Jun 2003
The Computer
3×131 Posts 
Quote:
Interesting as well! I have a 3060 Ti, but going to 92 bits would take about 10 weeks. We could test P1 to ensure it runs on Mlucas or other software and then go to 92 bits if there is hardware available to us that can complete P1 in a reasonable time frame thereafter. 

20211014, 05:31  #33  
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
2^{2}×3×13×37 Posts 
Quote:
I've been familiarizing with Mlucas V20.x and finding and reporting bugs and running P1 on "smaller" exponents. Like for other applications, Mlucas runtime scaling must be determined, and hardware coefficients determined, as preparation. Try doing the same. Including on the server you mentioned if you can have very extended and heavy use of it. (majority of cycles and ram occupancy for a year) There's not much point in attempting an OBD P1 run until those preparations are accomplished and fixes for most issues are provided for end users, especially the ram constraint I found. I expect P1 run times will be ~ several months to a year or more per attempt for good bounds depending on hardware and other loading. Also, there's no computing credit given or server reporting mechanism for P1 results (factor or nofactor) for exponents > 1G. 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
9596M to 64 bits.  chalsall  Lone Mersenne Hunters  1  20090908 02:28 
64 bits versus 32 bits Windows  S485122  Software  2  20061031 19:14 
3535.2 to 62 bits, cont from 61 bits  Khemikal796  Lone Mersenne Hunters  12  20051201 21:35 
26.126.3 to 62 Bits  derekg  Lone Mersenne Hunters  1  20040609 18:47 
5.98M to 6.0M: redoing factoring to 62 bits  GP2  Lone Mersenne Hunters  0  20031119 01:30 