20190413, 00:27  #1 
"Curtis"
Feb 2005
Riverside, CA
29·149 Posts 
Planning & Coordination for 2,2330L
We have a GNFS candidate from the Cunningham project at 207 digits:
Code:
334377437706404684733884220732190564550147039308686365251932207592010868660163280944362994773042289837865752943086095333357861608005044927356022538834108845220872215597190097852981295940487497385774178731621 I expect we'll oversieve this number enough to get matrix time down under 10 coreyears since a volunteer will be solving it on a single machine (that's me, unless fivemack has other ideas with his fastest machine). We have a C205 and C206 sieving on 16f at NFS@home presently, with Tom and I each committed to a matrix to finish the jobs. This provides us a natural comparison with CADO on this C207, the better to see how CADO compares to msieve for resource needs and time. swellman has scheduled a t65 on this number at yoyo; anyone eager to set an initial polyscore mark is invited to begin by reserving a coefficientrange on msieveGPU or CADO in this thread. If there is mediumterm interest in 2,1165+, we can coordinate poly select and such while we sieve 2,2330L. If CADO postprocessing proves unwieldy on resource needs or we find insufficient forumuser resources to sieve it, we can always send it to frmky and NFS@home for sieving. While ECM and poly select is going, we need to collectively decide whether to teamsieve with CADO, or send it to NFS@home. I *strongly* prefer a team sieve, for a few reasons: To learn how well CADO scales for future GNFS220+ tasks, because NFS@home already proved it can handle a number this size but we haven't, and because teamwork in this forum is fun. To decide it's worth proceeding as a CADOteamsieve, we ought to collect pledges from interested parties in units of coreyears. Sieve tasks will be handed out as a 4threaded job, using either 33.3GB of memory if I=15, or 1214GB if I=16. (We can select any fixed number of threads, and that number can be different for the I=15 server versus I=16) So, if you have a 16GB or greater machine, please estimate how many coreyears you can pledge for I=16 and complete within calendar 2019 (figure we'll start by 1 June, so 68 months for sieving). If you have 616GB ram, and wish to contribute, please pledge coreyears for I=15. We'll testsieve to find out how much less efficient I=15 is versus I=16; the CADO team factored RSA704 (GNFS212) entirely on I=15, though they noted the suboptimal parameters meant it took them 500 coreyears (eek!). This job is half as hard as GNFS212, so a wild guess is that I=15 work will be half as efficient as I=16 work. If we get pledges of I = 16 years + 0.5 * I=15 years = 80 or more, we can do this as a team sieve. Once we have a polynomial we can further refine this estimate via testsieving. Last fiddled with by VBCurtis on 20190413 at 00:30 
20190413, 00:30  #2 
"Curtis"
Feb 2005
Riverside, CA
10E1_{16} Posts 
I'm willing to put 20 cores toward this project, so I pledge 10 coreyears I=16.
I'll use this thread to track pledges: Code:
vbcurtis I=16 10 coreyears swellman I=16 2 coreyears RichD I=16 1 coreyear lukerichards I=16 2 coreyears ET I=16 4 coreyears fivemack I=16 30 coreyears Total: 49 coreyears Last fiddled with by VBCurtis on 20190519 at 04:03 
20190413, 00:50  #3 
Jun 2012
5×571 Posts 
I will pledge 4 cores for the duration.
Also reserving c5 < 1M for poly search using msieve. (I’m assuming we are not searching at all for a sextic.) 
20190413, 13:28  #4 
"Max"
Jun 2016
Toronto
701 Posts 
C207 CADO poly select 01M
Reserving c5 < 1M for poly search using CADO. (Later on I'll take 01M for a CADO sextic, just to see the difference. It would be great to have somebody testsieve topc5 vs topc6).

20190413, 15:49  #5 
"Curtis"
Feb 2005
Riverside, CA
29×149 Posts 
I'll surely testsieve a few top polys, at worst in 16f GGNFS but likely the best two will get testsieved in CADO to see if relative speed changes.

20190413, 17:12  #6 
"Max"
Jun 2016
Toronto
701_{10} Posts 
C207 score
@swellman
When you get to it, could you please post anything above 1e15? I am stuck at 7.68e16, and we are trying to get to 1.6e15. Quite probably my parameters are way off. 
20190413, 18:27  #7 
Jun 2012
5×571 Posts 

20190413, 20:12  #8 
Sep 2008
Kansas
2·7·13·17 Posts 
I'll pledge 4cores at half time. I guess that amounts to 1core year. This will work good for me since sometimes I have a box waiting 12, 24, 36 hours for sieving to complete at NFS@home and I can point it at the CADO server for a quick set of WUs (in addition to my pledge).
I'll start msieveGPU at c5=4M tomorrow when I get home. 
20190413, 21:13  #9 
"Luke Richards"
Jan 2018
Birmingham, UK
2^{5}·3^{2} Posts 
Minimum 2 core years from me.
I've never used the software mentioned, but I propose to get started on one of my home computers and probably later devote some Google Cloud credit to it Last fiddled with by lukerichards on 20190413 at 21:18 Reason: Inability to calculate 4 cores * 0.5 years! 
20190414, 15:32  #10  
"Max"
Jun 2016
Toronto
701 Posts 
C207 polys
Quote:
Code:
# norm 1.534672e20 alpha 7.343566 e 1.087e15 rroots 3 skew: 101089318.80 c0: 155816101167630939131941933802766181845255176400 c1: 24270336909414063210712346128763647493743 c2: 1941539569306237251183718679832592 c3: 41711829877443769945297129 c4: 265321259164440600 c5: 7695600 Y0: 24893355147235925339215203881525122029329 Y1: 25390484222442108467594 Code:
# norm 1.531481e20 alpha 7.344243 e 1.081e15 rroots 3 skew: 201773747.84 c0: 1238725398513114053251175452995353070314472059520 c1: 96455898644705516040804890845088702814652 c2: 3872983036737718442851378564937504 c3: 41754620765014257030865129 c4: 132659853865740300 c5: 1923900 Y0: 24893355147234901594891355015711708639249 Y1: 12695242111221054233797 

20190414, 23:05  #11 
"Max"
Jun 2016
Toronto
701 Posts 
C207 polys  first 1.2's
Code:
Y0: 19544845026703225729565432245313306145368 Y1: 10120116742258979082991 c0: 5973139622227297137449550863671749439844048257200 c1: 280720202442802238774504181104212579693210 c2: 1238186817666897836947815109808853 c3: 1780719008342744983579849 c4: 174906653491611360 c5: 123805440 skew 196606977.59 # size 1.416e20, alpha 8.218, combined = 1.205e15 rroots = 3 Code:
Y0: 9772422513351884893520748044014403870764 Y1: 10120116742258979082991 c0: 1497056890375551628851845387618418364676688307500 c1: 140293528523944498177067344182767951355725 c2: 1238477045246699046008488861071573 c3: 3636669026514306751748498 c4: 699759729575533440 c5: 990443520 skew 98182419.04 # size 1.427e20, alpha 8.240, combined = 1.203e15 rroots = 3 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Coordination thread for redoing P1 factoring  ixfd64  Lone Mersenne Hunters  50  20200610 21:01 
big job planning  henryzz  Cunningham Tables  16  20100807 05:08 
Sieving reservations and coordination  gd_barnes  No Prime Left Behind  2  20080216 03:28 
Sieved files/sieving coordination  gd_barnes  Conjectures 'R Us  32  20080122 03:09 
Special Project Planning  wblipp  ElevenSmooth  2  20040219 05:25 