mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Software (https://www.mersenneforum.org/forumdisplay.php?f=10)
-   -   Prime95 v30.4/30.5/30.6 (https://www.mersenneforum.org/showthread.php?t=26376)

axn 2021-04-21 07:58

[QUOTE=James Heinrich;576319]Yes, and yes. Largely untested in both cases of course, so let me know if you find something not working as it should.[/QUOTE]

Great. Thanks for the confirmation.

kruoli 2021-04-21 15:21

P+1 crashes for me when resuming from a save file in stage 2. That's on Windows 7, 64 bit, AVX FFT, example worktodo line: [C]
Pplus1=N/A,1,2,100069,-1,10000000,4000000000,1[/C]

Prime95 2021-04-21 19:30

[QUOTE=kruoli;576366]P+1 crashes for me when resuming from a save file in stage 2. That's on Windows 7, 64 bit, AVX FFT, example worktodo line: [C]
Pplus1=N/A,1,2,100069,-1,10000000,4000000000,1[/C][/QUOTE]

Fixed. Build 2 now available. Links in post #150.

nordi 2021-04-21 22:00

I'm testing PP1 with 30.6b2 on Linux and it looks good so far. Resuming in stage 2 worked and I can see the results on mersenne.org. :smile:

The only thing that's missing is automated work assignment. I cannot set the worker preference to PP1 and the manual assignment page also does not offer it.

nordi 2021-04-22 06:59

I got the first new factor with PP1:

P+1 found a factor in stage #2, B1=10000000, B2=1000000000.
[URL="https://www.mersenne.org/report_exponent/?exp_lo=287873&full=1"]M287873[/URL] has a factor: 167460871862758047584571103871 (P+1, B1=10000000, B2=1000000000)


As expected, the factor is very P+1 smooth:

167460871862758047584571103872: 2 2 2 2 2 2 2 3 7 149 31153 137737 1326817 73440613


That's 1 factor out of 73 attempts.

axn 2021-04-22 08:46

[QUOTE=nordi;576466]I got the first new factor with PP1:

P+1 found a factor in stage #2, B1=10000000, B2=1000000000.
[URL="https://www.mersenne.org/report_exponent/?exp_lo=287873&full=1"]M287873[/URL] has a factor: 167460871862758047584571103871 (P+1, B1=10000000, B2=1000000000)
[/QUOTE]

:party:

Incidentally, even the P-1 is kinda smooth-ish. A B1 of 60m (with a suitable sized B2) could have found it, but of course would've been a lot costlier.

masser 2021-04-22 12:55

[QUOTE=nordi;576466]I got the first new factor with PP1:
[/QUOTE]

Congrats! Running the early P+1 attempts is going to be so much fun.

kriesel 2021-04-22 13:30

[QUOTE=Prime95;576418]Fixed. Build 2 now available. Links in post #150.[/QUOTE]If it's not too much trouble, could it also log the other worktodo entry parameters present after B2 in the worker window? It's not logging the required nth_run parameter.
FYI, the server displays a [URL="https://www.mersenne.org/report_exponent/?exp_lo=103598543&exp_hi=&full=1"]stage1-only result[/URL] for my attempts.

Does build 2 also fix failure to resume in stage 1 from save files after the program interrrupts its own progress for benchmarking, finding all its save files to be bad as build 1 has in my initial testing? Possibly there was no save file saved before the start of benchmarking. That was preceded by some sort of crash that rendered it unusable until I commented out a worktodo entry. (Would not even appear on screen or in Task Manager displays; just hourglass cursor briefly.)
Worktodo for reference, with comments added:
[CODE][Worker #1]
;;Pplus1=N/A,1,2,103598543,-1,1000000,30000000,1 this line ran but 0.3GB default memory was too small for the 367MB stage 2 requirement, stage 2 skipped, and entry was removed by program
;;Pplus1=N/A,1,2,103598543,-1,1000000,30000000,2 this line crashed program and stopped successful relaunch until commented out
Pplus1=N/A,1,2,103598543,-1,1000000,30000000,3 this line ran and generated worker window contents shown below

;;Pplus1=N/A,1,2,103598543,-1,1000000,30000000,2 This line was always commented out, a saved copy

Pfactor=(AID),1,2,103598543,-1,76,2
DoubleCheck=(AID),61020931,74,1
[/CODE]Worker window contents from after the comment out of "Pplus1=N/A,1,2,103598543,-1,1000000,30000000,2" and restart, from entry "Pplus1=N/A,1,2,103598543,-1,1000000,30000000,3":
[CODE][Apr 22 00:05] Worker starting
[Apr 22 00:05] Setting affinity to run worker on CPU core #1
[Apr 22 00:05]
[Apr 22 00:05] P+1 on M103598543 with B1=1000000, B2=30000000
[Apr 22 00:05] Setting affinity to run helper thread 1 on CPU core #2
[Apr 22 00:05] Setting affinity to run helper thread 2 on CPU core #3
[Apr 22 00:05] Setting affinity to run helper thread 3 on CPU core #4
[Apr 22 00:05] Using AVX-512 FFT length 5760K, Pass1=3K, Pass2=1920, clm=1, 4 threads
[Apr 22 00:05] Error reading intermediate file: n103598543
[Apr 22 00:05] Renaming n103598543 to n103598543.bad1
[Apr 22 00:05] Trying backup intermediate file: n103598543.bu
[Apr 22 00:05] Error reading intermediate file: n103598543.bu
[Apr 22 00:05] Renaming n103598543.bu to n103598543.bad2
[Apr 22 00:05] Trying backup intermediate file: n103598543.bu2
[Apr 22 00:05] Error reading intermediate file: n103598543.bu2
[Apr 22 00:05] Renaming n103598543.bu2 to n103598543.bad3
[Apr 22 00:05] All intermediate files bad. Temporarily abandoning work unit.
[Apr 22 00:05] Optimal P-1 factoring of M103598543 using up to 8192MB of memory.
[Apr 22 00:05] Assuming no factors below 2^76 and 2 primality tests saved if a factor is found.
[Apr 22 00:05] Optimal bounds are B1=796000, B2=34294000
[Apr 22 00:05] Chance of finding a factor is an estimated 4.25%
[Apr 22 00:05]
[Apr 22 00:05] Using AVX-512 FFT length 5760K, Pass1=3K, Pass2=1920, clm=1, 4 threads
[Apr 22 00:05] Setting affinity to run helper thread 1 on CPU core #2
[Apr 22 00:05] Setting affinity to run helper thread 2 on CPU core #3
[Apr 22 00:05] Setting affinity to run helper thread 3 on CPU core #4
[Apr 22 00:05] M103598543 stage 1 is 0.07% complete.
[Apr 22 00:17] M103598543 stage 1 is 3.33% complete. Time: 732.338 sec.
[Apr 22 00:30] M103598543 stage 1 is 6.58% complete. Time: 748.808 sec.
[Apr 22 00:42] M103598543 stage 1 is 9.83% complete. Time: 754.124 sec.
[Apr 22 00:56] M103598543 stage 1 is 13.08% complete. Time: 805.479 sec.
[Apr 22 01:09] M103598543 stage 1 is 16.34% complete. Time: 798.707 sec.
[Apr 22 01:22] M103598543 stage 1 is 19.59% complete. Time: 772.745 sec.
[Apr 22 01:35] M103598543 stage 1 is 22.84% complete. Time: 770.437 sec.
[Apr 22 01:48] M103598543 stage 1 is 26.09% complete. Time: 765.248 sec.
[Apr 22 02:00] M103598543 stage 1 is 29.35% complete. Time: 747.334 sec.
[Apr 22 02:12] M103598543 stage 1 is 32.60% complete. Time: 745.663 sec.
[Apr 22 02:25] M103598543 stage 1 is 35.85% complete. Time: 744.883 sec.
[Apr 22 02:37] M103598543 stage 1 is 39.10% complete. Time: 744.670 sec.
[Apr 22 02:50] M103598543 stage 1 is 42.36% complete. Time: 740.006 sec.
[Apr 22 03:02] M103598543 stage 1 is 45.61% complete. Time: 735.905 sec.
[Apr 22 03:14] M103598543 stage 1 is 48.86% complete. Time: 737.190 sec.
[Apr 22 03:27] M103598543 stage 1 is 52.12% complete. Time: 738.341 sec.
[Apr 22 03:39] M103598543 stage 1 is 55.37% complete. Time: 741.178 sec.
[Apr 22 03:51] M103598543 stage 1 is 58.62% complete. Time: 739.355 sec.
[Apr 22 04:04] M103598543 stage 1 is 61.87% complete. Time: 741.066 sec.
[Apr 22 04:16] M103598543 stage 1 is 65.13% complete. Time: 740.033 sec.
[Apr 22 04:28] M103598543 stage 1 is 68.38% complete. Time: 742.332 sec.
[Apr 22 04:42] M103598543 stage 1 is 71.63% complete. Time: 812.386 sec.
[Apr 22 04:55] M103598543 stage 1 is 74.88% complete. Time: 813.312 sec.
[Apr 22 05:05] Worker stopped while running needed benchmarks.
[Apr 22 05:13] Benchmarks complete, restarting worker.
[Apr 22 05:13]
[Apr 22 05:13] P+1 on M103598543 with B1=1000000, B2=30000000
[Apr 22 05:13] Setting affinity to run helper thread 1 on CPU core #2
[Apr 22 05:13] Setting affinity to run helper thread 2 on CPU core #3
[Apr 22 05:13] Setting affinity to run helper thread 3 on CPU core #4
[Apr 22 05:13] Using AVX-512 FFT length 5760K, Pass1=3K, Pass2=1920, clm=1, 4 threads
[Apr 22 05:13] Trying backup intermediate file: n103598543.bad3
[Apr 22 05:13] Error reading intermediate file: n103598543.bad3
[Apr 22 05:13] Trying backup intermediate file: n103598543.bad2
[Apr 22 05:13] Error reading intermediate file: n103598543.bad2
[Apr 22 05:13] Trying backup intermediate file: n103598543.bad1
[Apr 22 05:13] Error reading intermediate file: n103598543.bad1
[Apr 22 05:28] M103598543 stage 1 is 2.21% complete. Time: 948.760 sec.
[Apr 22 05:44] M103598543 stage 1 is 4.51% complete. Time: 916.776 sec.
[Apr 22 05:59] M103598543 stage 1 is 6.82% complete. Time: 917.519 sec.
[Apr 22 06:14] M103598543 stage 1 is 9.13% complete. Time: 916.504 sec.
[Apr 22 06:30] M103598543 stage 1 is 11.44% complete. Time: 919.619 sec.
[Apr 22 06:45] M103598543 stage 1 is 13.73% complete. Time: 917.141 sec.
[Apr 22 07:00] M103598543 stage 1 is 16.03% complete. Time: 914.089 sec.
[Apr 22 07:15] M103598543 stage 1 is 18.35% complete. Time: 914.598 sec.
[Apr 22 07:31] M103598543 stage 1 is 20.64% complete. Time: 913.989 sec.
[Apr 22 07:46] M103598543 stage 1 is 22.92% complete. Time: 912.264 sec.
[/CODE]Will abandon the build 1 run and try again with build 2 shortly.

kriesel 2021-04-22 13:52

Build 2 calls all the build 1 P+1 save files bad. Perhaps resulting from a mismatch of nth_run parameter. I don't see anything in file naming that would prevent that mismatch from occurring.
Build 2 also calls bad, but appears to resume from its own stage 1 save file .bad(x) for same nth_run.
Test sequence:
Move all files marked bad. Launch prime95 30.6b2, with worktodo entry "Pplus1=N/A,1,2,103598543,-1,1000000,30000000,1" first in line.
Stop and exit. Restart.
Worker window contents from the restart:[CODE][Apr 22 08:56] Worker starting
[Apr 22 08:56] Setting affinity to run worker on CPU core #1
[Apr 22 08:56]
[Apr 22 08:56] P+1 on M103598543 with B1=1000000, B2=30000000
[Apr 22 08:56] Setting affinity to run helper thread 1 on CPU core #2
[Apr 22 08:56] Setting affinity to run helper thread 2 on CPU core #3
[Apr 22 08:56] Setting affinity to run helper thread 3 on CPU core #4
[Apr 22 08:56] Using AVX-512 FFT length 5760K, Pass1=3K, Pass2=1920, clm=1, 4 threads
[Apr 22 08:56] Error reading intermediate file: n103598543
[Apr 22 08:56] Renaming n103598543 to n103598543.bad1
[Apr 22 08:56] All intermediate files bad. Temporarily abandoning work unit.
[Apr 22 08:56]
[Apr 22 08:56] P+1 on M103598543 with B1=1000000, B2=30000000
[Apr 22 08:56] Setting affinity to run helper thread 1 on CPU core #2
[Apr 22 08:56] Setting affinity to run helper thread 2 on CPU core #3
[Apr 22 08:56] Setting affinity to run helper thread 3 on CPU core #4
[Apr 22 08:56] Using AVX-512 FFT length 5760K, Pass1=3K, Pass2=1920, clm=1, 4 threads
[Apr 22 08:56] Trying backup intermediate file: n103598543.bad1
[Apr 22 08:56] M103598543 stage 1 is 1.09% complete.
[/CODE]

ATH 2021-04-22 14:15

[QUOTE=kriesel;576485]If it's not too much trouble, could it also log the other worktodo entry parameters present after B2 in the worker window? It's not logging the required nth_run parameter.
FYI, the server displays a [URL="https://www.mersenne.org/report_exponent/?exp_lo=103598543&exp_hi=&full=1"]stage1-only result[/URL] for my attempts.[/QUOTE]

Are you using build 2 because it is logging B2 for me. The nth_run is also logged like this: nth_run=1 means Start=2/7 and nth_run=2 means: Start=6/5, so the initial seed is logged not the actually nth_run value.

kriesel 2021-04-22 14:53

1 Attachment(s)
[QUOTE=ATH;576490]Are you using build 2 because it is logging B2 for me. The nth_run is also logged like this: nth_run=1 means Start=2/7 and nth_run=2 means: Start=6/5, so the initial seed is logged not the actually nth_run value.[/QUOTE]I did not claim it hides B2. As a fresh install of v30.6b1 in a new folder, I forgot to reset the small default allowed memory at first, so it skipped [U]running[/U] stage 2 until that small memory limit was dealt with.
As stated previously, I have run prime95 v30.6b1 and v30.6b2 repeatedly. Neither indicated [B]nth_run[/B] [U]in the worker window[/U]. Ever. The one results.json.txt entry for the one stage1 completion so far indicates the corresponding start value. But the worker windows have never indicated the [B]nth_run[/B] parameter following the B2 value in the worktodo file's active line (or the corresponding start value in a worker window). So we must either deduce from the worker history or results file, or open the worktodo file, to see which worktodo line is currently in effect, of nth_run = 1, 2, or 3 for the same exponent/bounds set:
[CODE][Worker #1]
Pplus1=N/A,1,2,exponent,-1,B1,B2,[B]1[/B]
Pplus1=N/A,1,2,exponent,-1,B1,B2,[B]2[/B]
Pplus1=N/A,1,2,exponent,-1,B1,B2,[B]3[/B]
[/CODE]


All times are UTC. The time now is 04:23.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.