2019 14e post processing reservations and results

[RichD]

p60 factor: 171526815410477835938001571348443457525366849226788167577579
p179 factor: 14200414182299524548342530886185160299303470789991518003297954332014794455918770698469958500890035411056747078094988942581969682368197042043067112896781129515815286455521480878859

202M unique relations built a 10.05M matrix using TD=120. (TD=124 failed)
Solve time about 64 hours. (-t 4)

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

[RichD]

p91 factor: 1153262621487788806452504488868584029009920567811197028226004915104673570932815166721570269
p134 factor: 88948029257169433825214365176196720459447293850588482742007805692211962069884844072477916303753689884896849984681289142649181924266781

103M unique relations built a 7.6M matrix using TD=116. (TD=120 failed)
Solve time about 34 hours. (-t 4)

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

[RichD]

Taking 122385589_29m1.

[RichD]

p54 factor: 766638352308704302741556910357754563683359375634156519
p154 factor: 2282878021377969113213347214989507879805672693602766959205444363451195564846069841155679603451051955153399414662598275779100547215291320089936553560528283

191M relations built a 15.1M matrix using TD=114. (TD=116 failed).
Solve time about 138 hours. (-t 4)

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

[RichD]

Taking 112137511_31m1.

[RichD]

p84 factor: 567410276136798753167369416939022891233225796877805348824220805010902784692838839521
p126 factor: 211931366103205640473277090942217127577864746271770918943014001045961530688470959278039321632850773177700368461419205049839921

179.6M unique relations built a 12.8M matrix using TD=108. (TD=112 failed)
Solve time about 105 hours. (-t 4)

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

[jyb]

Taking 35466__6521_3m1.

[richs]

Originally Posted by richs

Another 10M Q added

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

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....

Looks like 20M extra Q wasn't enough:

skipped 4 relations with b > 2^32
skipped 611 relations with composite factors
found 41292894 hash collisions in 132382609 relations
added 1828991 free relations
commencing duplicate removal, pass 2
found 52281629 duplicates and 81929971 unique relations
memory use: 1193.5 MB
reading ideals above 104923136
commencing singleton removal, initial pass
memory use: 1506.0 MB
reading all ideals from disk
memory use: 1503.7 MB
commencing in-memory singleton removal
begin with 81929971 relations and 74864091 unique ideals
reduce to 44230161 relations and 32352028 ideals in 19 passes
max relations containing the same ideal: 26
reading ideals above 720000
commencing singleton removal, initial pass
memory use: 1378.0 MB
reading all ideals from disk
memory use: 1684.8 MB
keeping 44117302 ideals with weight <= 200, target excess is 223463
commencing in-memory singleton removal
begin with 44230167 relations and 44117302 unique ideals
reduce to 43623028 relations and 43508924 ideals in 21 passes
max relations containing the same ideal: 200
filtering wants 1000000 more relations
elapsed time 01:48:27

So for the third time, please add another 10M Q. Thanks.

[RichD]

Originally Posted by richs

So for the third time, please add another 10M Q. Thanks.

It looks like the last 10M Q only added about 2.6M unique. Perhaps a bit more would be in order.

[VBCurtis]

With lims as low as they are (FRMAX 33500000/FAMAX 67000000), and Q already at 170M, this job may need someone to do some offline 15e sieving below the Q=12M starting point. Yield of 0.26 is pretty terrible, but yield at low Q may be enough to salvage the job.

[RichD]

Originally Posted by VBCurtis

With lims as low as they are (FRMAX 33500000/FAMAX 67000000), and Q already at 170M, this job may need someone to do some offline 15e sieving below the Q=12M starting point. Yield of 0.26 is pretty terrible, but yield at low Q may be enough to salvage the job.

You are correct VBCurtis. I was going to ask richs if he wanted to do 256128979_23m1 instead and I would take over this number and perform some low level sieving after I got back in town next week. One or both of the "lim"s should have been increased in hindsight. My fault.