Since my role in factoring 4051^71-1 has so far been limited to poking and prodding others to commit their own resources, the least I can do is reserve it for post processing.

Edit: Oh wait, will it fit in 16 GiB...? I don't do large factorizations anywhere near enough to recall the answer of the top of my head

[QUOTE=Dubslow;420760]Since my role in factoring 4051^71-1 has so far been limited to poking and prodding others to commit their own resources, the least I can do is reserve it for post processing.

Edit: Oh wait, will it fit in 16 GiB...? I don't do large factorizations anywhere near enough to recall the answer of the top of my head[/QUOTE]

Yes it should fit easily in 16 Gb.

[QUOTE=swellman;420773]Yes it should fit easily in 16 Gb.[/QUOTE]

Neat. In that case, assuming that no one has reserved C175_4788_5241, then I would like to post process that one as well.

GC_4_376 done
 

Three-way split, which is a little unusual

[code]
Fri Jan 1 03:38:37 2016 prp58 factor: 1697918852793197192217323908495025258053565572486150252069
Fri Jan 1 03:38:37 2016 prp58 factor: 2082414812562347487534209948536765479560302299495190215491
Fri Jan 1 03:38:37 2016 prp73 factor: 6312408474500341106936815071249860914101269298101832313661343150269184973
[/code]

Sixteen or so hours for 5.3M matrix on i7/4790K, but don't believe this time because I forgot to stop mprime for the first few hours.

[PASTEBIN]xz65v9J6[/PASTEBIN]

[QUOTE=fivemack;420826]Three-way split, which is a little unusual
3,475+[/quote]
Indeed, though Rich Dickerson also had a 3-way split yesterday for GC_3_475 into p62 * p62 *p66.

Curious that adjacent entries in the 3+ table should behave like that.

Paul

GW_4_375 factored
 

22 hours to solve a 6.1M matrix on a Core-i5 (2500), -t 4 using target_density=112 (TD=120 failed).
[CODE]p112 factor: 4056928493609013958804639147971978303117812707562018799041101931093966442274853083123509995580542478762100510867
p116 factor: 49766600723887431286229655589628760624601439750538384432683252305743967895154190482041153258663513432598853842824527[/CODE]

Taking GC_6_290 and GC_6_291.

GC_6_291 done
 

[code]
Sun Jan 3 00:13:29 2016 prp67 factor: 7128029182287052712024884582525109111910095569550925881449077101221
Sun Jan 3 00:13:29 2016 prp116 factor: 10636651627022111863672091779433066677624021733172213386201935909099491351431923386843729789723539897838698109846617
[/code]

22.5 hours for 6.6M density-110 matrix on 4 threads i7/4770K

Log attached.

Taking GW_5_323, ETA Thursday evening

GW_4_377
 

[CODE]p59 factor: 83183733331118795763978354021097038819918862223784769031299
p120 factor: 614208831276238939388701945744049795019787238427208608225289996654837009564461039743982141601834688980252140038410069219[/CODE]

GC_6_290 done
 

[code]
Sun Jan 3 14:34:19 2016 p70 factor: 3838583084750444102740442464057059432973534582863054746119950413023069
Sun Jan 3 14:34:19 2016 p129 factor: 283816119704891256111630664948882422745194213705935241539967857502526755342090471257205774173006297665485778914972965504238027583
[/code]

47.3 hours on four cores not-completely-idle i7/750 (2.66GHz Nehalem) for a 6.93M density-120 matrix

[pastebin]LXCeDv8K[/pastebin]