20210602, 17:21  #474  
If I May
"Chris Halsall"
Sep 2002
Barbados
9928_{10} Posts 
Quote:
I've actually been using my fourteen (14#) (CPU only) Colab instances to clean up after those who complete an FTC without first doing a P1. Sometimes preemptively; in 103M for example... Let's talk about this over the weekend. Super busy at the moment. 

20210602, 20:13  #475 
"Carlos Pinho"
Oct 2011
Milton Keynes, UK
136B_{16} Posts 
Happy to join with 10 Colab sessions but will need some guidance.

20210602, 21:28  #476 
If I May
"Chris Halsall"
Sep 2002
Barbados
2^{3}·17·73 Posts 

20210603, 04:10  #477  
1976 Toyota Corona years forever!
"Wayne"
Nov 2006
Saskatchewan, Canada
2^{2}·3·397 Posts 
Quote:
The problem is that at this fine of a breakdown there are some serious outliers and so few exponents to work with. Not even trying I found for example (there are worse): 26.70M 232 Unfactored (33 to get under 200). Each bit level of TF will find about 2 factors with only 232 exponents. So via TF only that is 16 more bit levels....with luck maybe only 14. So that is TF 7387. That is almost 1,200,000 GhzDays per exponent; 8 months with my 2080Ti per exponent. Assuming we agree that is beyond reasonable we need to find some factors via P1. Lets say we want to save 7 bits of TF so we need about 14 P1 factors from these 232 exponents. We need about a 6% increase in current P1; so we will need to run P1 with a 10.5% expected success rate to be safe. That is 100GhzDays per exponent x 232 = 23,200 to get these 14 factors. The better part of a year for a reasonable PC. However there is another issue. TF and P1 can find the same factors so the more P1 that is done the lower the chance of finding a TF factor and vice versa. If we were to find these 14 P1 factors then the TF success rate will drop; or in other words it will not save 7 levels of TF. OKAY too much blabbering; you see where I'm going.  That all said maybe once the sub2000 project is complete the hardware will allow us to reconsider sub200. Thanks for your interest. 

20210603, 13:45  #478  
Romulan Interpreter
Jun 2011
Thailand
23054_{8} Posts 
Quote:
But I couldn't stop boasting about the P+1 success in 1.89M and about finding over 30 factors in 26M. Right now, they are more, as I moved to 27M and found 5 factors there today too. 

20210609, 14:21  #479 
Romulan Interpreter
Jun 2011
Thailand
2^{2}×7×349 Posts 
yarrr
This almost passed unobseved: Code:
1717043 FPP1 Start=2/7, B1=5000000, B2=365000000, Factor: 36120234091485938570203343 Last fiddled with by LaurV on 20210609 at 14:24 
20210610, 05:45  #480 
Jun 2003
2^{2}·5·257 Posts 
34m is done
The last two ranges 3.7 & 3.9 were done today, thus completing 34m.
I had some TF help from anonymous benefactor which greatly accelerated 3.9 range. Once the pending P1s from 3.7/3.9 ranges are completed (few days to couple of weeks), I'll move over to 4.1 range. I've been prepping that range with 6870 TF. 
20210612, 07:21  #481 
Romulan Interpreter
Jun 2011
Thailand
2^{2}×7×349 Posts 
Is anybody doing P1 in this range?
I found about 15 factors in the last 4 days, but only 11 of them are reflected in the table, therefore the 12th is from somebody else (I don't know which 12th). If that's a TF/P+1/ECM factor, no harm, but if that's a P1, then we are duplicating the efforts. I started when 2076 candidates were left and (after a discussion with Wayne on PM) I calculated my B1 and B2 to have a 100% theoretic chance of finding 77 factors, considering an average of the TF and P1 already done. Then, I "rounded up" them to "look nice", i.e. being prime, and containing a sequence of interesting primes too, as a substring that's how I ended with B1=2329319 (sorry, 313 was not prime), and B2=61891103 (107x was not prime, and 1103 is a factor of M29!). For who's asking. These are nice, round numbers. Don't tell me that numerology is not catchy! Joking apart, with the default TF of the range the two limits would have a chance to get a factor in 10 trials, but considering that the range was overfactored, to 74 bits, the chance is just 1 factor in about 17 or 18 trials. However, the range had average P1 done too, which "pulled out the low hanging fruits", so the real chance is somewhere at 1 in 23 to 1 in 26 (depending on the P1 already done for each, I didn't calculate exact, only took an "eye average"). This would cover for the 77 factors (which, in 2076, means 1 in about 26.9, plus the luck ). Up to now, it fits, with 77 factors to find I should find about 7.7 in every 35.1x range, and I have 15 in the first 2 ranges, plus a bit. Last fiddled with by LaurV on 20210612 at 07:56 
20210612, 08:20  #482 
Jun 2003
2^{2}·5·257 Posts 
Code:
35130749 227470147005389851276513 20210610 Sid & Andy FPM1 B1=1500000, B2=45000000 
20210612, 08:38  #483 
Jun 2003
2^{2}·5·257 Posts 
The real chance is more like 1 in 36, so you might find something like 60 factors. You could fall short by 15 factors in clearing this range with this P1.

20210612, 12:26  #484 
Romulan Interpreter
Jun 2011
Thailand
2^{2}×7×349 Posts 
Oh. Then I should either raise the limits, or save the checkpoint files to avoid work duplication in the future if me or somebody else will wish to extend the limits. BTW, can gpuOwl extend B1? (I remember getting errors like "wrong B1, using the one from saved checkpoint" or so).

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Thinking of Joining GPU to 72  jschwar313  GPU to 72  3  20160131 00:50 
Thinking about lasieve5  Batalov  Factoring  6  20111227 22:40 
Thinking about buying a panda  jasong  jasong  1  20081111 09:43 
Loud thinking on irregular primes  devarajkandadai  Math  4  20070725 03:01 
Question on unfactored numbers...  WraithX  GMPECM  1  20060319 22:16 