Update
 

- Lucas(1324) has been working on an overtasked machine, but is now cranking on 6 threads. Should be done in a few more weeks.

- C210 from 129^103+103^129 results reported today [b]updated[/b]

- C246 from 143^58+58^143 results reported in [url=http://www.mersenneforum.org/showpost.php?p=477273&postcount=2367]post 2367[/url] [b]updated[/b]

There will be a fortnight or so's delay for F1361; it uses 21GB of memory which turns out to be too much on a 32GB machine on which I'm building a several-million-line C++ codebase repeatedly, so I'll have to move it to another machine which is currently busy. The job will take about a month so the delay is immaterial.

[QUOTE=pinhodecarlos;478915]

Reserving 265*(9^265+1).C232, doing this for Paul.[/QUOTE]

LA underway, ETA 150 hours.

Looks like the GCW number (9_266+.C255) in the 14e queue can use a few more relations. Currently the 32-bit job is at 345M.

[QUOTE=RichD;479095]Looks like the GCW number (9_266+.C255) in the 14e queue can use a few more relations. Currently the 32-bit job is at 345M.[/QUOTE]

That’s why I’ve chosen to post process the one queued on the 15e queue. Paul needs to estimate more relations up to ~450M.

F1469 is complete:
[code]prp77 factor: 14707318795142178793712842139214249585232198901328179403254741435264239387637
prp107 factor: 12238715020863597403126410370715840499161703793870153678980148848432866729077776897334456680693270487543061
[/code]

Log at [url]https://pastebin.com/H2afkbvG[/url]

After remdups, roughly 385M unique relations remained. TD 134 produced a 20.1M matrix of density 71. So, I reduced relations available:
375M relations produced 19.35M of density 87
360M relations produced 18.8M of density 99
345M relations produced 18.5M of density 109
330M relations produced 17.3M of density 134
332M relations produced 17.22M of density 134
I used the last matrix. It consumed 9.1GB memory according to "top".

I don't think any 32-bit job needs more than 450M raw relations, and many of these will build nice matrices with 425M. We're oversieving by 15% beyond the relation set that will build 130+ density matrices, and inattentive postprocessors will waste substantial time solving the bigger matrices that result.

[QUOTE=VBCurtis;479133]F1469 is complete:
[code]prp77 factor: 14707318795142178793712842139214249585232198901328179403254741435264239387637
prp107 factor: 12238715020863597403126410370715840499161703793870153678980148848432866729077776897334456680693270487543061
[/code]

Log at [url]https://pastebin.com/H2afkbvG[/url]

After remdups, roughly 385M unique relations remained. TD 134 produced a 20.1M matrix of density 71. So, I reduced relations available:
375M relations produced 19.35M of density 87
360M relations produced 18.8M of density 99
345M relations produced 18.5M of density 109
330M relations produced 17.3M of density 134
332M relations produced 17.22M of density 134
I used the last matrix. It consumed 9.1GB memory according to "top".

I don't think any 32-bit job needs more than 450M raw relations, and many of these will build nice matrices with 425M. We're oversieving by 15% beyond the relation set that will build 130+ density matrices, and inattentive postprocessors will waste substantial time solving the bigger matrices that result.[/QUOTE]

Nice finding, consistent with your earlier work. I know that when posting “my” jobs the target number of relations is always high, 490-500M for 32-bit jobs. Future requests from me will target 450M going forward (I have few 31-bit jobs in the hopper, all GNFS C175-182 currently).

[QUOTE=swellman;479139]Nice finding, consistent with your earlier work. I know that when posting “my” jobs the target number of relations is always high, 490-500M for 32-bit jobs. Future requests from me will target 450M going forward (I have few 31-bit jobs in the hopper, all GNFS C175-182 currently).[/QUOTE]

It's worth pointing out for posterity that this job began with 484M raw relations; my log does not show that since remdups was run before filtering. The duplication rate of the highest/last Q is usually higher than the lower Q values, so it's reasonable to think that 410M raw relations would have yielded the 330-335M unique relations needed for the desired density of 134. This was a GNFS-183 job, so 175-180 jobs should aim for 400M or 410M raw relations.
This poly may have had unusually low duplication of relations, but it's a safe bet that a smaller job won't need more raw relations.

Reserving 144^55+55^144 C180 cofactor for postprocessing. Thank you.

C231_134_79 factored

[code]
prp63 factor: 121228617008936764925388482653465206046556191972729649438307283
prp169 factor: 5583421281472380925687498948836078361630770800617356324851941804728158677443434969099749217012072569073397018190430180207527906857723918495624214642334514406145094063491
[/code]

570995583 raw / 436934597 unique relations

Taking L1384 (ETA 20 February)