Taking 71316922984999_19m1.

9p8_263 is complete:


[CODE]p96 factor: 114345020076237245122698303527576255572518462367196354065838953180689595900805149287285385994347
p99 factor: 613574317597269180787833342550115992858931441912439099541084447117166573043502445226018207288523633[/CODE]
TD = 115 built a 14.98 M matrix (TD 118 failed) which took ~178.7 hours to solve. Log posted at [URL]https://pastebin.com/A89Zne4q[/URL] and [URL]https://github.com/Dylan1496/nfs-at-home-logs/blob/master/9p8_263.log[/URL].

5p3_1425M is complete:


[CODE]p72 factor: 135487664878054986754339693314817521369690946273460185439697766446147301
p84 factor: 312174572672771176467488450138669372024406788404132624609065101817431664308782305601[/CODE] TD 135 built a 3.39 M matrix (not TD 138) which took 5.068 hours to solve. Log posted at [URL]https://pastebin.com/W93RYpgz[/URL] and [URL="https://github.com/Dylan1496/nfs-at-home-logs/blob/master/5p3_1425M.log"]https://github.com/Dylan1496/nfs-at-home-logs/blob/master/5p3_1425M.log.[/URL]


Reserving 4391_59m1 for post-processing.

Taking 7p2_310

[QUOTE=jyb;519864]38160408950501_17m1 needs more sieving. Over 35% of the relations are duplicates, and msieve doesn't get very far in filtering before it complains. I'd probably add another 40M.

[B]Done.[/B][/QUOTE]

Well that additional 40M range of special-q resulted in only 26M additional relations. And of those, 14M were duplicates, so we only ended up with 12M more unique relations. Unsurprisingly, msieve is still unhappy with what we've got.

I would suggest more sieving, but at this point the returns are diminishing so fast that it's hard to know what to do. I'll defer to those who have more expertise with this sort of situation than I do.

[QUOTE=jyb;520267]Well that additional 40M range of special-q resulted in only 26M additional relations. And of those, 14M were duplicates, so we only ended up with 12M more unique relations. Unsurprisingly, msieve is still unhappy with what we've got.

I would suggest more sieving, but at this point the returns are diminishing so fast that it's hard to know what to do. I'll defer to those who have more expertise with this sort of situation than I do.[/QUOTE]

I'll take it and finish off the sieving locally at the low end. I just started another similar job (GNFS-180) and the solve time is about four weeks at TD=132. It may be a while before 71316922984999_19m1 gets off the board.

[QUOTE=RichD;520268]I'll take it and finish off the sieving locally at the low end. I just started another similar job (GNFS-180) and the solve time is about four weeks at TD=132. It may be a while before 71316922984999_19m1 gets off the board.[/QUOTE]

71316922984999_19m1 should finish up on Wednesday.

I would sieve 15-20M on 15e offline, and hope I get enough relations to build some sort of matrix, even if it's density 80 or 75.

[QUOTE=jyb;520269]71316922984999_19m1 should finish up on Wednesday.[/QUOTE]

Oh, sorry. When I looked at the status page I thought you only had one number and that was what you were talking about.

I'll still take 38160408950501_17m1 and complete it locally.

10p9_263 factored
 

[QUOTE=richs;519891]Taking 10p9_263[/QUOTE]

[CODE]p75 factor: 866648130990907026602460868640278341744990661866072865880553915041401854451
p80 factor: 91223392195546093727849684001010192222539538505027457458979422084992687926317167[/CODE]

Approximately 23.8 hours on 2 threads Core i3-2310M with 4 GB memory for a 4.10M matrix at TD = 70.

Log attached and at [URL="https://pastebin.com/hjwLPV53"]https://pastebin.com/hjwLPV53[/URL]

Factors added to FDB.

Taking 11m6_241.