2019 14e post processing reservations and results - Page 42

jyb · 2019-06-25, 06:09

Taking 71316922984999_19m1.

Dylan14 · 2019-06-25, 13:50

9p8_263 is complete:

Code:

p96 factor: 114345020076237245122698303527576255572518462367196354065838953180689595900805149287285385994347
p99 factor: 613574317597269180787833342550115992858931441912439099541084447117166573043502445226018207288523633

TD = 115 built a 14.98 M matrix (TD 118 failed) which took ~178.7 hours to solve. Log posted at https://pastebin.com/A89Zne4q and https://github.com/Dylan1496/nfs-at-...er/9p8_263.log.

Dylan14 · 2019-06-27, 20:14

5p3_1425M is complete:

Code:

p72 factor: 135487664878054986754339693314817521369690946273460185439697766446147301
p84 factor: 312174572672771176467488450138669372024406788404132624609065101817431664308782305601

TD 135 built a 3.39 M matrix (not TD 138) which took 5.068 hours to solve. Log posted at https://pastebin.com/W93RYpgz and https://github.com/Dylan1496/nfs-at-home-logs/blob/master/5p3_1425M.log.

Reserving 4391_59m1 for post-processing.

richs · 2019-06-28, 04:26

Taking 7p2_310

jyb · 2019-06-28, 18:04

Quote:

Originally Posted by jyb

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.

Done.

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.

RichD · 2019-06-28, 18:40

Quote:

Originally Posted by jyb

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.

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.

jyb · 2019-06-28, 18:44

Quote:

Originally Posted by RichD

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.

71316922984999_19m1 should finish up on Wednesday.

VBCurtis · 2019-06-28, 18:45

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.

RichD · 2019-06-28, 19:11

Quote:

Originally Posted by jyb

71316922984999_19m1 should finish up on Wednesday.

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.

richs · 2019-06-29, 02:39

Quote:

Originally Posted by richs

Taking 10p9_263

Code:

p75 factor: 866648130990907026602460868640278341744990661866072865880553915041401854451
p80 factor: 91223392195546093727849684001010192222539538505027457458979422084992687926317167

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 https://pastebin.com/hjwLPV53

Factors added to FDB.

jyb · 2019-06-29, 22:34

Taking 11m6_241.

2019-06-25, 13:50	#453
Dylan14 "Dylan" Mar 2017 1104₈ Posts	9p8_263 is complete: Code: p96 factor: 114345020076237245122698303527576255572518462367196354065838953180689595900805149287285385994347 p99 factor: 613574317597269180787833342550115992858931441912439099541084447117166573043502445226018207288523633 TD = 115 built a 14.98 M matrix (TD 118 failed) which took ~178.7 hours to solve. Log posted at https://pastebin.com/A89Zne4q and https://github.com/Dylan1496/nfs-at-...er/9p8_263.log.

2019-06-27, 20:14	#454
Dylan14 "Dylan" Mar 2017 2²·5·29 Posts	5p3_1425M is complete: Code: p72 factor: 135487664878054986754339693314817521369690946273460185439697766446147301 p84 factor: 312174572672771176467488450138669372024406788404132624609065101817431664308782305601 TD 135 built a 3.39 M matrix (not TD 138) which took 5.068 hours to solve. Log posted at https://pastebin.com/W93RYpgz and https://github.com/Dylan1496/nfs-at-home-logs/blob/master/5p3_1425M.log. Reserving 4391_59m1 for post-processing.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
2018 15e post-processing reservations and results	fivemack	NFS@Home	221	2019-01-04 13:08
2018 14e post processing reservations and results	pinhodecarlos	NFS@Home	551	2019-01-04 13:06
16e Post Processing Progress	pinhodecarlos	NFS@Home	8	2018-11-28 13:45
Update on 7^254+1 post processing	dleclair	NFSNET Discussion	4	2005-04-05 09:51
Post processing for 2,757-	xilman	NFSNET Discussion	3	2003-11-06 14:23

2019-06-25, 06:09	#452
jyb Aug 2005 Seattle, WA 3·19·31 Posts	Taking 71316922984999_19m1.

2019-06-28, 04:26	#455
richs "Rich" Aug 2002 Benicia, California 10100101000₂ Posts	Taking 7p2_310

2019-06-28, 18:45	#459
VBCurtis "Curtis" Feb 2005 Riverside, CA 2×2,437 Posts	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.

2019-06-29, 22:34	#462
jyb Aug 2005 Seattle, WA 3·19·31 Posts	Taking 11m6_241.