View Single Post
Old 2019-05-20, 02:04   #15
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

5,923 Posts
Default Why don't we occasionally manually submit progress reports for long-duration manual primality tests?

There's currently no way to do that.
This is a CUDALucas console output line:
Code:
|  May 19  20:00:49  |  M49602851  30050000  0x05c21ef8e9eac8b2  |  2688K  0.15625   2.0879  104.39s  |     11:15:47  60.58%  |
https://www.mersenne.org/manual_result/ does not understand it. It responds as follows:
Done processing:
* Parsed 1 lines.
* Found 0 datestamps.

GHz-days Qty Work Submitted Accepted Average 0 - all - 0.000
  • Did not understand 1 lines.
  • Recognized, but ignored 0/0 of the remaining lines.
  • Skipped 0 lines already in the database.
  • Accepted 0 lines.
There's no way to report progress of a GPU-based manual primality test or lengthy P-1 factoring run or long TF run, so from the PrimeNet server's point of view, progress remains at 0.0%. This means sometimes they prematurely expire. It would be useful if the manual results processing script would accept progress reports in CUDALucas console output form as in the example above, even if it was limited to accepting reports with iteration counts that were multiples of 1M or 10M. See also https://www.mersenneforum.org/showthread.php?t=24262

Accepting Gpuowl progress records would also be very useful. Since there has been considerable variation in log record format versus Gpuowl version, selecting a very small number of the most popular reliable efficient versions may be in order. I suggest V6.11-380 and V7.2-53. PRP seems most important to support, since first time PRPs can be time consuming, and PRPDC currently gets subjected to Cat0 short expiration periods without any progress reporting occurring.

Gpuowl v6.11-380 log records (PRP followed by LL):

Code:
2021-05-24 19:46:20 asr2/radeonvii0 59234033 OK 38500000  64.99%;  599 us/it; ETA 0d 03:27; ec9cffdc371be8e4 (check 1.34s)
2020-06-03 22:21:09 asr2/radeonvii0 91844033 LL   400000   0.44%;  697 us/it; ETA 0d 17:43; de6590c819df3895
Gpuowl V7.2-53 log record example of most use is the last style below in bold:
Code:
2021-01-02 18:40:07 asr2/radeonvii0 510004423 OK   3000000   0.59% 20d8f6ecf29974cf 7658 us/it + check 3.50s + save 6.33s; ETA 44d 22:33 | P1(3M) 69.3% ETA 02:50 b7f0461995a6dae4
2021-01-02 18:42:44 asr2/radeonvii0 510004423      3010000   0.59% d1ee8d164b98cfc2 15756 us/it
2021-01-02 18:45:22 asr2/radeonvii0 510004423      3020000   0.59% 41dd444c0d2bbf1e 15793 us/it
2021-01-02 18:46:34 asr2/radeonvii0 510004423 P1 Jacobi OK @ 3000000 b7f0461995a6dae4
...
2021-01-02 21:51:31 asr2/radeonvii0 510004423 P2(3M,130M)   0.8%  7530 muls, 7533 us/mul, ETA 13:32
...
2021-01-04 11:04:13 asr2/radeonvii0 510004423 P2(3M,130M) Starting GCD
2021-01-04 11:04:14 asr2/radeonvii0 510004423 P2(3M,130M) Released memory lock 'memlock-0'
...
2021-01-15 03:34:28 asr2/radeonvii0 510004423      4990000   0.98% 56b05ac1fec0d4e7 6555 us/it
2021-01-15 03:35:37 asr2/radeonvii0 510004423 OK   5000000   0.98% 54713855d68e7cdb 6294 us/it + check 3.49s + save 2.09s; ETA 36d 18:59
Top of this reference thread: https://www.mersenneforum.org/showth...736#post510736
Top of reference tree: https://www.mersenneforum.org/showpo...22&postcount=1

Last fiddled with by kriesel on 2021-05-27 at 17:59 Reason: added gpuowl versions, examples
kriesel is online now