2019 14e post processing reservations and results - Page 24

RichD · 2019-03-23, 15:18

unconnected · 2019-03-23, 23:11

Taking 9p8_301.

RichD · 2019-03-24, 19:56

Can we get a little bit more relations on 9173_61m1? I had to go down to TD=116 and it built a 15.5M matrix with ETA just over 230 hours. It would be nice to do a 31-bit job in under a week.

Done. Added another 10M Q.

RichD · 2019-03-25, 13:42

Taking 11681692691969_17m1.

RichD · 2019-03-25, 16:59

A few more relations are needed for 11681692691969_17m1. It only has 164M unique and does not build a matrix at TD=120. The previous mentioned one above (9173_61m1) had 184M unique before more was added. I think something in the 190Ms would be a good target.

These octics do generate a higher dup rate but they are more beneficial than the traditional sextic because the SNFS difficulty is dropped by the size of the base number -- and it sieves better...

frmky · 2019-03-25, 17:53

Quote:

Originally Posted by swellman

Strange that. 11681692691969_17m1 is also an octic, and it is missing A7 and A8 in the .fb as well. Does NFS@Home use an older version of msieve?

The ggnfs->msieve format converter assumed a max degree of 6. I've modified it to support octics, so future octics should output the correct msieve fb file.

RichD · 2019-03-29, 13:30

Taking 36739_53m1.

RichD · 2019-03-29, 19:24

Code:

p54 factor: 392885230626022337474134843895579500900837536034472419
p177 factor: 661996674789898688096080018887447669840298243155848718729572256683560486164943183063917756283619110821586908564865557293492312391853662291179147885922042830757434745259430250293

383M unique relations buit a 16.2M matrix using TD=116.
Solve time about 172 hours. (-t 4)

Log at: https://pastebin.com/tvKjxkgS

RichD · 2019-03-31, 21:09

Taking 2917_67m1.

richs · 2019-04-01, 03:23

Another 10M Q added

The extra 10M Q wasn't enough for 4784213763211_17m1 at TD=70:

Code:

Sun Mar 31 19:17:46 2019  skipped 4 relations with b > 2^32
Sun Mar 31 19:17:46 2019  skipped 583 relations with composite factors
Sun Mar 31 19:17:46 2019  found 39240373 hash collisions in 128858589 relations
Sun Mar 31 19:17:46 2019  commencing duplicate removal, pass 2
Sun Mar 31 19:25:27 2019  found 49252825 duplicates and 79605764 unique relations
Sun Mar 31 19:25:27 2019  memory use: 724.8 MB
Sun Mar 31 19:25:27 2019  reading ideals above 94568448
Sun Mar 31 19:25:27 2019  commencing singleton removal, initial pass
Sun Mar 31 19:47:41 2019  memory use: 1506.0 MB
Sun Mar 31 19:47:41 2019  reading all ideals from disk
Sun Mar 31 19:48:22 2019  memory use: 1498.1 MB
Sun Mar 31 19:48:31 2019  commencing in-memory singleton removal
Sun Mar 31 19:48:36 2019  begin with 79605764 relations and 75181859 unique ideals
Sun Mar 31 19:49:24 2019  reduce to 40506210 relations and 30858674 ideals in 19 passes
Sun Mar 31 19:49:24 2019  max relations containing the same ideal: 26
Sun Mar 31 19:49:29 2019  reading ideals above 720000
Sun Mar 31 19:49:30 2019  commencing singleton removal, initial pass
Sun Mar 31 20:06:35 2019  memory use: 1378.0 MB
Sun Mar 31 20:06:35 2019  reading all ideals from disk
Sun Mar 31 20:07:05 2019  memory use: 1540.7 MB
Sun Mar 31 20:07:13 2019  keeping 41529152 ideals with weight <= 200, target excess is 203963
Sun Mar 31 20:07:19 2019  commencing in-memory singleton removal
Sun Mar 31 20:07:24 2019  begin with 40506216 relations and 41529152 unique ideals
Sun Mar 31 20:08:47 2019  reduce to 39931866 relations and 40953698 ideals in 17 passes
Sun Mar 31 20:08:47 2019  max relations containing the same ideal: 200
Sun Mar 31 20:08:51 2019  filtering wants 1000000 more relations
Sun Mar 31 20:08:51 2019  elapsed time 01:25:25

Please Sir, I want some more....

unconnected · 2019-04-01, 09:51

9p8_301 completed - 132 hours for 12.4M matrix (TD=140).

Code:

p105 factor: 994214001887647745096531311846054571357577299721777026792438194443790607813273643824410371936800412656753
p136 factor: 3865503147101622630768025865801963467659702589166875896152410398807058194056060074845531475642929818170712830875929182081393223051403833

https://pastebin.com/6AjrVdjB

2019-03-23, 15:18	#254
RichD Sep 2008 Kansas 2×3×5×113 Posts	2879_61m1 results https://pastebin.com/v47M11A5

2019-03-24, 19:56	#256
RichD Sep 2008 Kansas 2×3×5×113 Posts	Can we get a little bit more relations on 9173_61m1? I had to go down to TD=116 and it built a 15.5M matrix with ETA just over 230 hours. It would be nice to do a 31-bit job in under a week. Done. Added another 10M Q. Last fiddled with by swellman on 2019-03-24 at 20:00

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-03-23, 23:11	#255
unconnected May 2009 Russia, Moscow 2,593 Posts	Taking 9p8_301.

2019-03-25, 13:42	#257
RichD Sep 2008 Kansas 2·3·5·113 Posts	Taking 11681692691969_17m1.

2019-03-25, 16:59	#258
RichD Sep 2008 Kansas 3390₁₀ Posts	A few more relations are needed for 11681692691969_17m1. It only has 164M unique and does not build a matrix at TD=120. The previous mentioned one above (9173_61m1) had 184M unique before more was added. I think something in the 190Ms would be a good target. These octics do generate a higher dup rate but they are more beneficial than the traditional sextic because the SNFS difficulty is dropped by the size of the base number -- and it sieves better...

2019-03-29, 13:30	#260
RichD Sep 2008 Kansas 110100111110₂ Posts	Taking 36739_53m1.

2019-03-31, 21:09	#262
RichD Sep 2008 Kansas 2×3×5×113 Posts	Taking 2917_67m1.