![]() |
[QUOTE=Batalov;295998]Neat. As luck has it. (I had 3800 11e6s on it already ATM.)
Now a little one? [strike]C116?[/strike] C113? :-)[/QUOTE] I set it factor(C142), ECM found the P29, and YAFU's already started GNFS on the C113, so I'll let it crunch. Edit: I'd estimate a few hours tops, maybe even less than 1 hr, but it's late; we'll see. [code]<poly select> aprogs: 2511 entries, 3391 roots hashtable: 4096 entries, 0.06 MB coeff 10212 specialq 1 - 3943 other 6499 - 15597 aprogs: 1030 entries, 1358 roots hashtable: 1024 entries, 0.02 MB coeff 10212 specialq 1 - 684 other 15597 - 37432 aprogs: 2427 entries, 3235 roots hashtable: 4096 entries, 0.06 MB coeff 10224 specialq 1 - 3945 other 6498 - 15595 aprogs: 1064 entries, 1404 roots hashtable: 1024 entries, 0.02 MB coeff 10224 specialq 1 - 684 other 15595 - 37428 aprogs: 2509 entries, 3381 roots hashtable: 4096 entries, 0.06 MB coeff 10248 specialq 1 - 3949 other 6496 - 15590 aprogs: 1086 entries, 1570 roots hashtable: 2048 entries, 0.03 MB coeff 10248 specialq 1 - 685 other 15590 - 37416 aprogs: 2609 entries, 4025 roots <snip> nfs: commencing polynomial search over range: 11001 - 11251[/code] It keeps spitting ~1 line/sec. The snip represents about a minute of output. Edit: Aw crap, crost post/cross NFS. You'll have to tell me which one of us is further. I'll post when it starts sieving. (One core of a ~3.9 GHz 2600K.) |
:popcorn:
[code]#free gift (a.k.a. poison): # norm 9.458633e-11 alpha -5.536770 e 7.531e-10 rroots 5 skew: 29634.48 c0: -65184430402097431471159344 c1: 24104275333618597871334 c2: 1628340288089389017 c3: -55394166360497 c4: -1696239259 c5: 24924 Y0: -4986425138116492873961 Y1: 227709451789[/code] |
[QUOTE=Batalov;296007]My bet is on you! ...'cause you know... nobody else is running it. ;-)[/QUOTE]
We cross posted ... :razz: edit: me and akruppa cross posted. Man, this is full of cross posting and editing. Unfortunately, I don't actually know how to pass that polynomial to yafu/ggnfs, nor if it's better than anything I've found :razz: I was originally going to edit this to say that C105s take roughly 1100 seconds for poly select; so this'll take 1500, 1800? 20-30 mins. [code]nfs: commencing polynomial search over range: 21001 - 21251[/code] Edit-who-knows-which: [strike]The only two numbers close are the quintic coeff and the skew (I have no idea what that is, I'm only guessing on the coeffs.) Which does my line of code refer to?[/strike] Edit5004: It says limit 50 CPU-seconds per coeff. Edit5005: Whoops, I just actually read the output I copied pasted and answered my own question :blush: EditILoveEdits!: [code]hashtable: 4096 entries, 0.06 MB coeff [U]24924[/U] specialq 1 - 5979 other 5770 - 13848 aprogs: 916 entries, 1152 roots[/code] Edit5007: Regarding 5005, I gotta ask, what do the others besides the coefficients mean? Which do you use to "measure how good" a poly is? Edit0800: Jeez, how far does poly select go? I'm at 56.5K and climbing! Edit0811: Okay, I'm going to cheat a bit. At sometime not after sieving starts, I'm putting all four cores on it. Edit0818: 80K and climbing... |
Have 1M relations so far. I estimate about 2-3 more hours of sieving.
|
And in the meantime, my edit time is up, and 93K coeff and climbing... and my roommate wants bed... you win :smile:
|
Done
|
Did 1600@3M on c121, starting NFS. Feel free to do more ECM to get factors sooner.
Edit: sieving about half done, factors some time tomorrow. |
Done
Edit: starting NFS on c110. |
Done
|
i3000
|
Doing NFS on c99. @bsquared: Oh, good!
|
| All times are UTC. The time now is 23:15. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.