Prime95 v30.3

[Uncwilly]

Originally Posted by Xyzzy

Is there a worktype option to select proof work?

Select DC or PRP-CF-DC and it is a freebie that you get. There are not enough being generated to keep the Cert runners flush with work. If you want to generate the proofs, just do first time checks with the latest version.

[intelfx]

Experienced the priority issue again:

Aug 13 07:06:17 stratofortress.nexus.i.intelfx.name mprime[69751]: [Work thread Aug 13 07:06] Running Jacobi error check.  [Aug 13 07:06] Sending expected completion date for M110701609: Aug 24 2020
Aug 13 07:06:18 stratofortress.nexus.i.intelfx.name mprime[69751]: [Comm thread Aug 13 07:06] PrimeNet success code with additional info:
Aug 13 07:06:18 stratofortress.nexus.i.intelfx.name mprime[69751]: [Comm thread Aug 13 07:06] Server assigned CERT work.
Aug 13 07:06:18 stratofortress.nexus.i.intelfx.name mprime[69751]: [Comm thread Aug 13 07:06] Got assignment 55203D43C36D845B45BCF307EAB00E67: CERT M10445371
Aug 13 07:06:18 stratofortress.nexus.i.intelfx.name mprime[69751]: [Comm thread Aug 13 07:06] Done communicating with server.
Aug 13 07:06:41 stratofortress.nexus.i.intelfx.name mprime[69751]: [Work thread] Passed.  Time: 24.635 sec.
Aug 13 07:06:41 stratofortress.nexus.i.intelfx.name mprime[69751]: [Work thread Aug 13 07:06] Resuming primality test of M109983959 using FMA3 FFT length 6M, Pass1=1536, Pass2=4K, clm=1, 16 threads
Aug 13 07:06:41 stratofortress.nexus.i.intelfx.name mprime[69751]: [Work thread Aug 13 07:06] Iteration: 62704259 / 109983959 [57.01%].
Aug 13 07:06:58 stratofortress.nexus.i.intelfx.name mprime[69751]: [Work thread Aug 13 07:06] Iteration: 62710000 / 109983959 [57.01%], ms/iter:  2.909, ETA: 38:11:38
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name systemd[1]: Stopping mprime.service...
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[69751]: [Main thread Aug 13 07:07] Stopping all worker windows.
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[69751]: [Work thread Aug 13 07:07] Stopping primality test of M109983959 at iteration 62718308 [57.02%]
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[69751]: [Work thread Aug 13 07:07] Worker stopped.
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[69751]: [Main thread Aug 13 07:07] Execution halted.
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[69751]: [Main thread Aug 13 07:07] Choose Test/Continue to restart.
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name systemd[1]: mprime.service: Succeeded.
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name systemd[1]: Stopped mprime.service.
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name systemd[1]: mprime.service: Consumed 10min 46.312s CPU time.

Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name systemd[1]: Started mprime.service.
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[70335]: [Main thread Aug 13 07:07] Mersenne number primality test program version 30.3
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[70335]: [Main thread Aug 13 07:07] Optimizing for CPU architecture: AMD Zen, L2 cache size: 16x512 KB, L3 cache size: 4x16 MB
Aug 13 07:07:22 stratofortress.nexus.i.intelfx.name mprime[70335]: [Main thread Aug 13 07:07] Starting worker.
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Worker starting
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run worker on CPU core #1
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 1 on CPU core #2
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 3 on CPU core #4
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 4 on CPU core #5
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 5 on CPU core #6
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 6 on CPU core #7
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 7 on CPU core #8
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 8 on CPU core #9
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 9 on CPU core #10
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 10 on CPU core #11
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 11 on CPU core #12
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 12 on CPU core #13
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 13 on CPU core #14
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 14 on CPU core #15
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 15 on CPU core #16
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Setting affinity to run helper thread 2 on CPU core #3
Aug 13 07:07:23 stratofortress.nexus.i.intelfx.name mprime[70335]: [Work thread Aug 13 07:07] Starting certification of M10445371 using FMA3 FFT length 560K, Pass1=448, Pass2=1280, clm=1, 16 threads

That is: mprime does not attempt to work on the newly received CERT assignment unless manually restarted (at which point the CERT assignment(s) are performed first regardless of their position in worktodo.txt, which suggests priority behavior.)


Would like to know if this is a bug or intended behavior.

[Prime95]

Originally Posted by intelfx

That is: mprime does not attempt to work on the newly received CERT assignment unless manually restarted (at which point the CERT assignment(s) are performed first regardless of their position in worktodo.txt, which suggests priority behavior.)

Would like to know if this is a bug or intended behavior.

I believe mprime checks for priority work once an hour.

[kriesel]

[Tue Aug 11 15:57:12 2020]
Unexpected error during upload: {"error_status":401,"error_message":"Unauthorized","error_description":""}

It would be good if it told in that case, what exponent's proof file it was trying to upload at the time, such as by giving the file name: "Unexpected error during upload of file nnnnnnnn-l.proof:". (Some of us have prime95 instances with multiple workers. Some of us may be using prime95 to upload proofs from gpuowl.)

Also, I do not see any subsequent log entry of successful upload, in prime.log, results.txt, or results.json.txt. I think this was for a gpuowl proof file for 138000061.

[Uncwilly]

I just upgraded a machine to v30.3 (from 29) and it started to do TF on some of the PRP-CF's that were queued up.

[Prime95]

Originally Posted by Uncwilly

I just upgraded a machine to v30.3 (from 29) and it started to do TF on some of the PRP-CF's that were queued up.

Odd. What did the worktodo.txt lines look like?

In the meantime, put "SkipTrialFactoring=1" in prime.txt

[Uncwilly]

They look like this now:

PRP=AID,1,2,10445909,-1,64,0,"1158749967781922153929"
PRP=AID,1,2,10447607,-1,64,0,"709324882075208391407"
PRP=AID,1,2,3360769,-1,99,0,3,5,"7420577953,1976985451084487,121365941392574291033"
PRP=AID,1,2,2902771,-1,59,0,"17643545420524016638023623"
PRP=AID,1,2,10459489,-1,64,0,"1082825031643242155311"
PRP=AID,1,2,4713857,-1,99,0,3,5,"141415711,2441360721372359,121781663060087391769"
PRP=AID,1,2,5300761,-1,99,0,3,5,"22263196201,121673322749022149191"
PRP=AID,1,2,5453839,-1,99,0,3,5,"261784273,121728904184791573927"
PRP=AID,1,2,5706013,-1,99,0,"19480328383,296438787377,5191111836037529,12979380910552501759,121716143484835542329"
PRP=AID,1,2,5943127,-1,99,0,"7630067053284433,121645664538289521281"

Before hand I think some did not have the 99 (or other number) in place. It did not run those that have the 99. But it did do the exponents that had other numbers up to the normal P95 limit. It also seemed to have dropped the assignments where it found factors.

Yeah for beta!!!

And BTW, except Windows "Defender", the corporate antivirus and Symantec/Norton Insight did not squawk about the files from mersenne.org like they did from dropbox.

[storm5510]

Originally Posted by ATH

CERT for PRP-CF for a 10.48M exponent took 18 sec on 8 cores, so 2.5 min tops if running it on a single core, and maybe 3-5 minutes at most if you have a very old cpu and running it on 1 core.

A person will not always get a certification for a cofactor if they are running the same. I ran a certify yesterday, 166-million and change, on my i5 which took 5 hours to complete. I run only cofactor tests. I do not have the CPU horsepower many others here have. I have no qualms about running them

About proof file names. I have noticed most are prefixed with "pA" while a few others are just "p." Both carry the .proof extension. There must be a difference. When Prime95 sends a certification with "pA" in front, a text line appears indicating the transfer was successful. This does not happen with the latter. They also assume the same file title as the backup files.

Since George straightened me out, I have had no problems.


Edit: Correction. Prime95 does give details about the sending of proof files with the "p" prefix.

[kriesel]

Originally Posted by storm5510

I ran a certify yesterday, 166-million and change, on my i5 which took 5 hours to complete.

(166000013 Thank you!)

[Prime95]

Originally Posted by Uncwilly

They look like this now:

PRP=AID,1,2,10445909,-1,64,0,"1158749967781922153929"
PRP=AID,1,2,10447607,-1,64,0,"709324882075208391407"
PRP=AID,1,2,3360769,-1,99,0,3,5,"7420577953,1976985451084487,121365941392574291033"
PRP=AID,1,2,2902771,-1,59,0,"17643545420524016638023623"
PRP=AID,1,2,10459489,-1,64,0,"1082825031643242155311"
PRP=AID,1,2,4713857,-1,99,0,3,5,"141415711,2441360721372359,121781663060087391769"
PRP=AID,1,2,5300761,-1,99,0,3,5,"22263196201,121673322749022149191"
PRP=AID,1,2,5453839,-1,99,0,3,5,"261784273,121728904184791573927"
PRP=AID,1,2,5706013,-1,99,0,"19480328383,296438787377,5191111836037529,12979380910552501759,121716143484835542329"
PRP=AID,1,2,5943127,-1,99,0,"7630067053284433,121645664538289521281"

How did you get these assignments? From prime95 contacting PrimeNet, or manually, or copied from http://mersenne.org/workload ?

For PRP-CF the how far factored field should always be 99. Certainly it should be at least the TJAOI minimum of 65 or 66.

[Uncwilly]

Originally Posted by Prime95

How did you get these assignments? From prime95 contacting PrimeNet, or manually, or copied from http://mersenne.org/workload?

Those came from through Prime95 contacting PrimeNet in the last few days. (I was away from the machine at the time. That was before I upgraded the machine to v30 at all. I looked at some where my machine found factors and TJAOI found some in the last few hours, so, my assignment was outdated.