20190506, 13:38  #89 
Oct 2015
2^{2}·17 Posts 
The other search finished with a better result:
Code:
n: 334377437706404684733884220732190564550147039308686365251932207592010868660163280944362994773042289837865752943086095333357861608005044927356022538834108845220872215597190097852981295940487497385774178731621 skew: 90705738.104 c0: 1655806548611327099132761402215592900502578257381 c1: 52470495453826760641954000116286955196049 c2: 2231551453970891751386654271420177 c3: 14227214675229453474894697 c4: 156074030035019784 c5: 209438460 Y0: 5445783017586151955857680467799412431984 Y1: 1986069033319259592352867 # MurphyE (Bf=3.436e+10,Bg=1.718e+10,area=5.469e+16) = 1.66e08 # found by revision 9436c2ff8 # f(x) = 209438460*x^5156074030035019784*x^4+14227214675229453474894697*x^3+2231551453970891751386654271420177*x^252470495453826760641954000116286955196049*x1655806548611327099132761402215592900502578257381 # g(x) = 1986069033319259592352867*x5445783017586151955857680467799412431984 
20190506, 14:06  #90 
"Curtis"
Feb 2005
Riverside, CA
2×47^{2} Posts 
Woohoo! Better, indeed:
skew 125540505.77018 score 1.64996072e15 (from cownoise) Have fun, Max! 
20190507, 03:32  #91  
"Max"
Jun 2016
Toronto
2BD_{16} Posts 
C207 poly
Quote:


20190507, 03:35  #92 
"Max"
Jun 2016
Toronto
701 Posts 
C207 polys
@vebis
I saw both "a" and "b" archives today, I need some time to get through all of it, but I am on it. 
20190507, 11:07  #93  
"Max"
Jun 2016
Toronto
701 Posts 
C207 poly
Quote:
Code:
Y0: 5445783020173886700337776518838434019565 Y1: 7944276133277038369411468 c0: 24745062283834793771655911246007349221232259556 c1: 3638239206861172772594019092164033469860 c2: 543588643271079731014156451777817 c3: 15037081380967059802226545 c4: 618838392632323536 c5: 3351015360 skew: 32629082.89 # size 2.319e20, alpha 7.604, combined = 1.671e15 rroots = 5 

20190507, 22:14  #94 
"Max"
Jun 2016
Toronto
1275_{8} Posts 
C207 poly
Another good poly from the "b" set after quick spin:
Code:
Y0: 6953261233697294683233295851584886174163 Y1: 5449957752208337629271462 c0: 1176061595709660314420928059407660349865025132200 c1: 37018662928190758651845113316638013040603 c2: 3268300215862651204474916762601600 c3: 38535057956097926521820731 c4: 316032307475148672 c5: 246874320 skew: 112240485.75 # size 2.361e20, alpha 8.390, combined = 1.663e15 rroots = 5 
20190508, 00:22  #95  
Jun 2012
101100111010_{2} Posts 
Quote:
The C211 and C217 are also on yoyo’s radar now, perhaps to be scheduled for ECM later this spring. 

20190509, 22:47  #96 
"Curtis"
Feb 2005
Riverside, CA
2·47^{2} Posts 
The machine that will host this job just finished sieving a C186 with CADO.
I=15, 32/33LP, Q=12195M produced 675M raw relations, 450M unique. About 6 hours of filtering (max memory use 31GB of 64GB physical) yielded a 22.0M matrix, which is now solving on CADO. CADO's matrix step has 3 parts: krylov, lingen, mksol. Krylov is using about 16GB, and will need 2 weeks to complete. lingen uses the most memory of the three, so I will wait for lingen to complete before considering firing up the CADO server for 2230L. Krylov is about 65% of the matrix step, so the job should yield factors by 1 June. Back to 2230L: I'm testsieving the bestscoring deg 5 this weekend, while hoping Max's spin yields a 1.7 from Vebis' new batch. Hopefully, we can test client connections in 710 days, and start the project roughly 1 June. 
20190509, 22:54  #97 
"Max"
Jun 2016
Toronto
2BD_{16} Posts 
C207

20190511, 04:34  #98  
"Curtis"
Feb 2005
Riverside, CA
4418_{10} Posts 
Quote:
So, I fired up simultaneous CADO instances, one 4threaded sieve on deg 6 (a fresh run, not continuing the old one) and one on deg 5. Both at Q=200M. After about half a million relations found, deg 6 yields 5.6 or so, while deg 5 yields 6.1. The ETAs are amusingly similar: April 20 2039 for deg 6, April 3 2039 for deg 5. I guess we'll call it a tie. I learned that reducing qmin on the snapshot file does not cause smaller Qranges to be added to the database. Then I tried changing qmin to 300M in a snapshot file; I'm pleased to report that the next workunit added to database was 300M! So, I'm comparing these two topscoring polys at Q=300M overnight. So, a multiQ test sieve can be achieved by starting the project at the minimum Q. Run your test, note results, kill job. Edit snapshot file qmin to the next Qvalue you wish to test, resume job. Yay! 

20190513, 03:23  #99 
"Curtis"
Feb 2005
Riverside, CA
2·47^{2} Posts 
Some more testsieving shows the deg 6 poly is marginally faster at the same Q as the highestscoring deg 5, but the deg 5 has 710% better yield. Better yield means more relations found at the lower & faster Q values, making up the 23% speed difference. Basically, it's a tie; we could choose the deg 6 if we wanted to do a 6thdegree job.
I tested I=15 vs I=16 at Q=300M. I=15 is some 30% faster! If we assume that we'll need 15% more relations from I=15 due to higher duplicate rate, there's still a strong argument for using I=15 for the higher Q values. In fact, I=15 is faster at Q=500M than I=16 is at Q=200M! I currently plan on I=16 from Q=10M to 200M, and then I=15 for the remaining Q. This gives us higher yield on the most fruitful Q values, and faster sieving with less memory on the back half of the job. We should find ~1.3G relations from 10200M at average yield of 6.5 or so, followed by 200950M at average yield of just under 2.0 to get the other 1.4G relations. This combination (pending details like testsieving 600 to 900M) appears to reduce expected sieve time to 4548 coreyears from a previous estimate of 5255. I'm testing Vebis' 1.65score deg 5 posted last week presently. 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Coordination thread for redoing P1 factoring  ixfd64  Lone Mersenne Hunters  53  20201030 19:39 
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 