20210222, 21:12  #12  
Oct 2019
5×7 Posts 
Quote:
After the default yafu deadline (15 hours on 16 threads), it came up with the following poly: Code:
# norm 1.864542e14 alpha 7.790576 e 5.755e12 rroots 1 n: 1426043462513149352725343828346122135124558025180582540209975486916412579335442554643075028986048822653001446339523289767395539874538318883219584088397 skew: 4873964.97 c0: 7702032464013727904646074499263003328 c1: 6599971977986952199257338715048 c2: 4593489433867649139114326 c3: 537224032042179013 c4: 134834027824 c5: 19740 Y0: 148510470184210525642080088739 Y1: 12432880281567133 rlim: 26400000 alim: 26400000 lpbr: 29 lpba: 29 mfbr: 58 mfba: 58 rlambda: 2.6 alambda: 2.6 Last fiddled with by jagotu on 20210222 at 21:14 

20210222, 22:23  #13 
"Curtis"
Feb 2005
Riverside, CA
11174_{8} Posts 
I attach my c150 params here.
I've tested similar settings just once so far, and they required 46 hours to factor a C150 (first digit 8) on a 12core haswellxeon2.5Ghz. Poly select was almost exactly 5% of the total job time, allowing you to extrapolate after poly select to estimate how long the job will take. My regression expects ~44hr for the sample job, so I made a couple changes after my one test before posting the file. Hopefully I went the right direction! Edit: You can use the file by replacing the file in cado/parameters/factor/ with this file. Rename to remove the ".txt" first that is just to pass the forum attachmentfilter. Last fiddled with by VBCurtis on 20210222 at 22:24 
20210222, 22:37  #14  
Oct 2019
100011_{2} Posts 
Quote:
EDIT: Reading your message, it seems to me that the 15 hours of 16core polyselect yafu did was a tiny bit overkill. CADO ETAs of polyselect are more in the 2 hours ballpark. Last fiddled with by jagotu on 20210222 at 22:44 

20210223, 11:13  #15 
Oct 2019
5×7 Posts 
CADO came up with a sligthly better poly:
Code:
n: 1426043462513149352725343828346122135124558025180582540209975486916412579335442554643075028986048822653001446339523289767395539874538318883219584088397 skew: 340540.367 c0: 13937828370359837949600476725853504 c1: 50954052566490822206230114856 c2: 525298205446344715893599 c3: 1736437202523857339 c4: 2200500511872 c5: 1935360 Y0: 97915003859407256007196314734 Y1: 1531204466924584393079 # MurphyE (Bf=2.147e+09,Bg=1.074e+09,area=2.013e+14) = 5.852e07 # f(x) = 1935360*x^52200500511872*x^4+1736437202523857339*x^3+525298205446344715893599*x^250954052566490822206230114856*x13937828370359837949600476725853504 # g(x) = 1531204466924584393079*x97915003859407256007196314734 
20210223, 17:23  #16 
Apr 2020
2·113 Posts 
The MurphyE scores from msieve and CADO aren't directly comparable  in fact this has a slightly worse score than the msieve poly (5.584e12 according to cownoise.com). But that's not surprising given the msieve poly search was so much longer.

20210224, 19:04  #17 
Oct 2019
43_{8} Posts 
Well... The sieving finished after some 48 hours, but then CADO ran out of disk space in the duplicate removal phase.
I increased the disk space and thought that restarting the same command will continue the job but nope, it deleted everything. Or maybe it was because I used the tmp folder to store the data. That was so dumb. I'll rerun it with the msieve poly this time. Last fiddled with by jagotu on 20210224 at 19:07 
20210224, 19:28  #18 
"Curtis"
Feb 2005
Riverside, CA
127C_{16} Posts 
We've all learned that /tmp lesson with CADO I'm extra sad for you that you learned it on a C150.
My lesson was given by a power outage 3 days in to a 4machineday job. 
20210224, 21:37  #19  
"Ed Hall"
Dec 2009
Adirondack Mtns
111001100100_{2} Posts 
Quote:
The /tmp directory will disappear with a computer reset. But, a new run of CADONFS will choose a new random /tmp/name, if not told where. If you had not reset the computer the old /tmp/folder would still be there and the snapshot file would begin at where the interruption occurred. I'm guessing that the memory increase was physical, but if not, you may still have the original CADONFS run. BTW, (some) changes in parameters can be made in the snapshot file, prior to restarting. Edit: In rereading, I see you increased disk space, not memory, so maybe the original /tmp folder still exists. Last fiddled with by EdH on 20210224 at 21:48 

20210225, 08:28  #20 
Oct 2019
100011_{2} Posts 
It was an azure VM, which I had to reboot to increase the disk size, which deleted the /tmp folder. So yeah it's gone, but I learned a lesson.

20210227, 09:09  #21 
Oct 2019
5×7 Posts 
i1415 C150
Factored the C150
Code:
Info:Complete Factorization / Discrete logarithm: Total cpu/elapsed time for entire factorization: 2.86374e+06/538.16 11789310602681804082021411295029741905179850745183857921041083704139694914489992339 120960716921713506158744867362986272316460242431288299728492494411423 
20210227, 14:45  #22  
"Ed Hall"
Dec 2009
Adirondack Mtns
2^{2}×3×307 Posts 
Quote:


Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Aliquot sequence reservations  schickel  Aliquot Sequences  3438  20210413 22:04 
Another Aliquot Sequence site  schickel  Aliquot Sequences  67  20120120 17:53 
Aliquot sequence worker for factordb  yoyo  FactorDB  6  20120112 20:58 
YA aliquotsequencechasing script  fivemack  Aliquot Sequences  5  20090928 16:40 
Useful aliquotsequence links  10metreh  Aliquot Sequences  2  20090731 17:43 