![]() |
![]() |
#23 |
(loop (#_fork))
Feb 2006
Cambridge, England
13·491 Posts |
![]() Code:
Thu May 24 14:41:46 2018 p81 factor: 659111171162587511001945202207366819602644411964225065081001137913325383295838909 Thu May 24 14:41:46 2018 p148 factor: 1672581374250702824738947742798076127330974868661411511817845162122621949046858328275460764421317767711434935811885774187181548411457277922503957077 I just took the first 400M relations rather than trying more complicated pre-filtering analyses. |
![]() |
![]() |
#24 | |
(loop (#_fork))
Feb 2006
Cambridge, England
13×491 Posts |
![]() Quote:
I hope there is some degree of 'running on this potato' in the runtimes ... 1300 hours would deal with a 50M matrix on my larger machines. If it's still >1000 hours for the job then I would happily take it over and run it on something chunkier. |
|
![]() |
![]() |
#25 | |
Jun 2012
52·7·17 Posts |
![]() Quote:
Last fiddled with by swellman on 2018-05-24 at 16:21 |
|
![]() |
![]() |
#26 |
AKA Speedy51
Oct 2012
New Zealand
3×73 Posts |
![]()
Reserving C198_756xx781_11 Thanks
|
![]() |
![]() |
#27 | |
Jun 2012
52·7·17 Posts |
![]() Quote:
With ~484M relations, TD=130 shows an ETA of 937 hrs. Not sure this time can be improved significantly. Reading in more relations and/or higher TD would likely help a bit but when traded against the time to optimize conditions, all under the cloud of possible oversieving lead me to think going with what I got might be best. But I’m open to investigating all scenarios if it’s helpful to others. Last fiddled with by swellman on 2018-05-25 at 12:06 |
|
![]() |
![]() |
#28 |
Jun 2012
52·7·17 Posts |
![]() |
![]() |
![]() |
#29 |
Sep 2009
3D116 Posts |
![]()
I have removed the reservation for C212_157xx799_13.
|
![]() |
![]() |
#30 |
Jun 2012
52×7×17 Posts |
![]()
Thank you.
|
![]() |
![]() |
#31 |
"Rich"
Aug 2002
Benicia, California
22·307 Posts |
![]() Code:
p80 factor: 13745796595569657487046976086814644298188282962356651514984076906025347008147003 p111 factor: 930761774694254454289678294527788495654974849663089855154505082398340025888249556096804633684441558318426871251 Log attached and log at https://pastebin.com/1QsvP734 Factors reported to factor database. |
![]() |
![]() |
#32 |
AKA Speedy51
Oct 2012
New Zealand
3×73 Posts |
![]()
I am going to have a guess and say this job took 4 1/2 hours. Starting the job with 8 cores and finished with 15 just to see if there was much time difference and there wasn't
Code:
p70 factor: 1989774706154817243345988310685771699308514675731245500652616051195507 p129 factor: 187207251745133606157391653086769259037917392116430983143576943217585815557363013773039151703724781592509357752386497852063522527 |
![]() |
![]() |
#33 |
(loop (#_fork))
Feb 2006
Cambridge, England
11000111011112 Posts |
![]()
As a person making essential use of Pastebin, and because they have a cheap offer at the moment, I've bought a lifetime PRO account for sixteen pounds. Apologies if I can't figure out how to drive it and accidentally produce, for example, pastes that aren't world-readable.
|
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
2018 15e post-processing reservations and results | fivemack | NFS@Home | 221 | 2019-01-04 13:08 |
16e Post Processing Progress | pinhodecarlos | NFS@Home | 8 | 2018-11-28 13:45 |
Crash doing large post-processing job | wombatman | Msieve | 22 | 2013-12-04 01:37 |
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 |