OFFICIAL "SERVER PROBLEMS" THREAD - Page 132

tha · 2018-03-21, 23:15

mprime was set to use 2,5 GB of ram which is more than sufficient to run this exponent with this B1/B2 setting. Can someone try this on his/ her machine? Could it be that the known factors are used as settings that don't make sense? Or that the line in worktodo should be constructed differently?

Dubslow · 2018-03-21, 23:54

Quote:

Originally Posted by chalsall

Fuck me.

That's what you get for using a text editor instead of those fancy new fangled "user interfaces"

James Heinrich · 2018-03-22, 00:03

Quote:

Originally Posted by tha

mprime was set to use 2,5 GB of ram which is more than sufficient to run this exponent with this B1/B2 setting. Can someone try this on his/ her machine? Could it be that the known factors are used as settings that don't make sense? Or that the line in worktodo should be constructed differently?

Your worktodo line looks fine. I didn't let it run to stage2 to see how much RAM it actually used. My P-1 probably calculator said it needs 186MB, would like 555MB, and wouldn't use more than 4536MB even if it was available.

Running your worktodo as-is seemed to start fine:

Code:

Setting affinity to run worker on logical CPUs 2 (zero-based)
P-1 on M22351237 with B1=400000, B2=9000000
Using AVX FFT length 1152K, Pass1=384, Pass2=3K, clm=1
M22351237 stage 1 is 0.557385% complete.

and restructured to a normal pick-its-own-bounds P-1 it picked:

Code:

Optimal P-1 factoring of M22351237 using up to 10000MB of memory.
Assuming no factors below 2^69 and 2 primality tests saved if a factor is found.
Optimal bounds are B1=215000, B2=3923750
Chance of finding a factor is an estimated 3.45%
Using AVX FFT length 1152K, Pass1=384, Pass2=3K, clm=1

Prime95 · 2018-03-22, 00:11

Quote:

Originally Posted by tha

mprime was set to use 2,5 GB of ram which is more than sufficient to run this exponent with this B1/B2 setting.

Do you have different day and nighttime settings? Do you have a memory setting for that particular worker?

tha · 2018-03-22, 10:34

I had copied the file

Code:

mM351237

to the new directory. That file contained the data from the previous run on that exponent with the B1=400000 and B2=8000000 setting and done with

Code:

Linux,Prime95,v28.9,build 2

I renamed that file now so it will not be used in a new run. It started stage 1 correctly an I will watch it over the next hours.

tha · 2018-03-22, 12:08

Same result. It first found the existing factors in stage1. I then restarted the assignment with Stage1GCD=0 added to prime.txt file. It still comes back with

Code:

Insufficient memory to ever run stage 2.
Stage 2 GCD complete. Time: 40.764 sec.
[Work thread Mar 22 12:39] P-1 found a factor in stage #2, B1=400000, B2=400000.
[Work thread Mar 22 12:39] M22351237 has a factor: 288476702225081262023002950746197048091558084285203081 (P-1, B1=400000, B2=400000)

These last setting B1=B2=400000 it generates itself every time.

So I now renamed the file mM351237 again and restarted the assignment with the Stage1GCD=0 setting before embarking on stage 1.

I have daytime and nighttime both set to 2560MB.

If setting a memory for a worker involves some kind of tweaking through the menu or in prime.txt than I would have remembered since this download and install took place yesterday.

tha · 2018-03-22, 14:07

Also does not result in a start of stage2. Removing the known factors is the only way to start stage2, even with B2=12000000. However, we wanted to start the line with the known factors in place, to test if the server will accept the higher B1/B2 bounds for inclusion in the data available on the exponent.

error · 2018-03-22, 14:34

Known factors should be put in between quotation marks: ...,"known,factors"

tha · 2018-03-22, 15:40

Quote:

Originally Posted by error

Known factors should be put in between quotation marks: ...,"known,factors"

Yep, that works!

Now wait and see what the server will store once the client makes the report.

chalsall · 2018-03-22, 19:51

Quote:

Originally Posted by James Heinrich

Your worktodo line looks fine. I didn't let it run to stage2 to see how much RAM it actually used. My P-1 probably calculator said it needs 186MB, would like 555MB, and wouldn't use more than 4536MB even if it was available.]

I ran it on one of my machines, with 12GB of RAM available, with the requested parameters.

Found a factor after stage 1. Interestingly, these results we're reported by Primenet. I suspect this is because they are already known.

Code:

[Main thread Mar 21 19:40] Mersenne number primality test program version 29.4
[Main thread Mar 21 19:40] Optimizing for CPU architecture: Core i3/i5/i7, L2 cache size: 256 KB, L3 cache size: 6 MB
[Main thread Mar 21 19:40] Starting worker.
[Work thread Mar 21 19:40] Worker starting
[Work thread Mar 21 19:40] Setting affinity to run worker on CPU core #1
[Work thread Mar 21 19:40] P-1 on M22351237 with B1=400000, B2=9000000
[Work thread Mar 21 19:40] Using AVX FFT length 1152K, Pass1=384, Pass2=3K, clm=1, 4 threads
[Work thread Mar 21 19:40] Setting affinity to run helper thread 3 on CPU core #4
[Work thread Mar 21 19:40] Setting affinity to run helper thread 2 on CPU core #3
[Work thread Mar 21 19:40] Setting affinity to run helper thread 1 on CPU core #2
[Work thread Mar 21 19:41] M22351237 stage 1 is 1.73% complete. Time: 38.006 sec.
[Work thread Mar 21 19:41] M22351237 stage 1 is 3.46% complete. Time: 28.800 sec.
[Work thread Mar 21 19:42] M22351237 stage 1 is 5.19% complete. Time: 27.955 sec.
[Work thread Mar 21 19:42] M22351237 stage 1 is 6.92% complete. Time: 28.137 sec.
[Work thread Mar 21 19:43] M22351237 stage 1 is 8.66% complete. Time: 29.200 sec.
[Work thread Mar 21 19:43] M22351237 stage 1 is 10.39% complete. Time: 29.818 sec.
[Work thread Mar 21 19:44] M22351237 stage 1 is 12.12% complete. Time: 28.841 sec.
[Work thread Mar 21 19:44] M22351237 stage 1 is 13.85% complete. Time: 28.288 sec.
[Work thread Mar 21 19:45] M22351237 stage 1 is 15.59% complete. Time: 27.570 sec.
[Work thread Mar 21 19:45] M22351237 stage 1 is 17.32% complete. Time: 27.334 sec.
[Work thread Mar 21 19:45] M22351237 stage 1 is 19.05% complete. Time: 26.511 sec.
[Work thread Mar 21 19:46] M22351237 stage 1 is 20.78% complete. Time: 26.816 sec.
[Work thread Mar 21 19:46] M22351237 stage 1 is 22.52% complete. Time: 27.140 sec.
[Work thread Mar 21 19:47] M22351237 stage 1 is 24.25% complete. Time: 26.725 sec.
[Work thread Mar 21 19:47] M22351237 stage 1 is 25.98% complete. Time: 26.483 sec.
[Work thread Mar 21 19:48] M22351237 stage 1 is 27.71% complete. Time: 27.906 sec.
[Work thread Mar 21 19:48] M22351237 stage 1 is 29.44% complete. Time: 26.641 sec.
[Work thread Mar 21 19:49] M22351237 stage 1 is 31.18% complete. Time: 27.229 sec.
[Work thread Mar 21 19:49] M22351237 stage 1 is 32.91% complete. Time: 27.801 sec.
[Work thread Mar 21 19:50] M22351237 stage 1 is 34.64% complete. Time: 30.414 sec.
[Work thread Mar 21 19:50] M22351237 stage 1 is 36.37% complete. Time: 29.186 sec.
[Work thread Mar 21 19:50] M22351237 stage 1 is 38.11% complete. Time: 28.209 sec.
[Work thread Mar 21 19:51] M22351237 stage 1 is 39.84% complete. Time: 27.703 sec.
[Work thread Mar 21 19:51] M22351237 stage 1 is 41.57% complete. Time: 27.121 sec.
[Work thread Mar 21 19:52] M22351237 stage 1 is 43.30% complete. Time: 26.914 sec.
[Work thread Mar 21 19:52] M22351237 stage 1 is 45.04% complete. Time: 27.352 sec.
[Work thread Mar 21 19:53] M22351237 stage 1 is 46.77% complete. Time: 28.310 sec.
[Work thread Mar 21 19:53] M22351237 stage 1 is 48.50% complete. Time: 27.263 sec.
[Work thread Mar 21 19:54] M22351237 stage 1 is 50.23% complete. Time: 26.834 sec.
[Work thread Mar 21 19:54] M22351237 stage 1 is 51.96% complete. Time: 30.217 sec.
[Work thread Mar 21 19:55] M22351237 stage 1 is 53.70% complete. Time: 26.946 sec.
[Work thread Mar 21 19:55] M22351237 stage 1 is 55.43% complete. Time: 28.055 sec.
[Work thread Mar 21 19:56] M22351237 stage 1 is 57.16% complete. Time: 34.969 sec.
[Work thread Mar 21 19:56] M22351237 stage 1 is 58.89% complete. Time: 26.830 sec.
[Work thread Mar 21 19:57] M22351237 stage 1 is 60.63% complete. Time: 26.890 sec.
[Work thread Mar 21 19:57] M22351237 stage 1 is 62.36% complete. Time: 27.189 sec.
[Work thread Mar 21 19:58] M22351237 stage 1 is 64.09% complete. Time: 34.326 sec.
[Work thread Mar 21 19:58] M22351237 stage 1 is 65.82% complete. Time: 28.445 sec.
[Work thread Mar 21 19:59] M22351237 stage 1 is 67.56% complete. Time: 26.598 sec.
[Work thread Mar 21 19:59] M22351237 stage 1 is 69.29% complete. Time: 30.539 sec.
[Work thread Mar 21 20:00] M22351237 stage 1 is 71.02% complete. Time: 32.876 sec.
[Work thread Mar 21 20:00] M22351237 stage 1 is 72.75% complete. Time: 30.036 sec.
[Work thread Mar 21 20:01] M22351237 stage 1 is 74.49% complete. Time: 26.737 sec.
[Work thread Mar 21 20:01] M22351237 stage 1 is 76.22% complete. Time: 26.565 sec.
[Work thread Mar 21 20:01] M22351237 stage 1 is 77.95% complete. Time: 27.443 sec.
[Work thread Mar 21 20:02] M22351237 stage 1 is 79.68% complete. Time: 26.631 sec.
[Work thread Mar 21 20:02] M22351237 stage 1 is 81.41% complete. Time: 28.904 sec.
[Work thread Mar 21 20:03] M22351237 stage 1 is 83.15% complete. Time: 26.724 sec.
[Work thread Mar 21 20:03] M22351237 stage 1 is 84.88% complete. Time: 27.368 sec.
[Work thread Mar 21 20:04] M22351237 stage 1 is 86.61% complete. Time: 27.381 sec.
[Work thread Mar 21 20:04] M22351237 stage 1 is 88.34% complete. Time: 27.092 sec.
[Work thread Mar 21 20:05] M22351237 stage 1 is 90.08% complete. Time: 26.649 sec.
[Work thread Mar 21 20:05] M22351237 stage 1 is 91.81% complete. Time: 26.547 sec.
[Work thread Mar 21 20:05] M22351237 stage 1 is 93.54% complete. Time: 26.653 sec.
[Work thread Mar 21 20:06] M22351237 stage 1 is 95.27% complete. Time: 26.456 sec.
[Work thread Mar 21 20:06] M22351237 stage 1 is 97.01% complete. Time: 26.728 sec.
[Work thread Mar 21 20:07] M22351237 stage 1 is 98.74% complete. Time: 26.603 sec.
[Work thread Mar 21 20:07] M22351237 stage 1 complete. 1154518 transforms. Time: 1624.137 sec.
[Work thread Mar 21 20:07] Stage 1 GCD complete. Time: 7.497 sec.
[Work thread Mar 21 20:07] P-1 found a factor in stage #1, B1=400000.
[Work thread Mar 21 20:07] M22351237 has a factor: 288476702225081262023002950746197048091558084285203081 (P-1, B1=400000)
[Comm thread Mar 21 20:07] Sending result to server: UID: wabbit/burrow, M22351237 has a factor: 288476702225081262023002950746197048091558084285203081 (P-1, B1=400000)
[Comm thread Mar 21 20:07]

tha · 2018-03-22, 20:22

The test completed without any new factors found. As far as I can see the new B1/B2 limits were not accepted by the server, either because the exponent was not reserved or for any other reason. What would be desired is the server accepting the new B1/B2 limits.

Code:

[Work thread Mar 22 20:44] Stage 2 GCD complete. Time: 41.600 sec.
[Work thread Mar 22 20:44] M22351237 completed P-1, B1=400000, B2=12000000, E=6, Wg2: 42FE55FE
[Comm thread Mar 22 20:44] Sending result to server: UID: Tha/Riet-Ubuntu, M22351237 completed P-1, B1=400000, B2=12000000, E=6, Wg2: 42FE55FE
[Comm thread Mar 22 20:44] 
[Comm thread Mar 22 20:44] PrimeNet error 40: No assignment
[Comm thread Mar 22 20:44] P-1 result for M22351237 was not needed

2018-03-22, 10:34	#1446
tha Dec 2002 5·163 Posts	I had copied the file Code: mM351237 to the new directory. That file contained the data from the previous run on that exponent with the B1=400000 and B2=8000000 setting and done with Code: Linux,Prime95,v28.9,build 2 I renamed that file now so it will not be used in a new run. It started stage 1 correctly an I will watch it over the next hours.

2018-03-22, 12:08	#1447
tha Dec 2002 32F₁₆ Posts	Same result. It first found the existing factors in stage1. I then restarted the assignment with Stage1GCD=0 added to prime.txt file. It still comes back with Code: Insufficient memory to ever run stage 2. Stage 2 GCD complete. Time: 40.764 sec. [Work thread Mar 22 12:39] P-1 found a factor in stage #2, B1=400000, B2=400000. [Work thread Mar 22 12:39] M22351237 has a factor: 288476702225081262023002950746197048091558084285203081 (P-1, B1=400000, B2=400000) These last setting B1=B2=400000 it generates itself every time. So I now renamed the file mM351237 again and restarted the assignment with the Stage1GCD=0 setting before embarking on stage 1. I have daytime and nighttime both set to 2560MB. If setting a memory for a worker involves some kind of tweaking through the menu or in prime.txt than I would have remembered since this download and install took place yesterday.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Official "Faits erronés dans de belles-lettres" thread	ewmayer	Lounge	39	2015-05-19 01:08
Official "all-Greek-to-me Fiction Literature and Cinema" Thread	ewmayer	Science & Technology	41	2014-04-16 11:54
Official "Lasciate ogne speranza" whinge-thread	cheesehead	Soap Box	56	2013-06-29 01:42
Official "Ernst is a deceiving bully and George is a meanie" thread	cheesehead	Soap Box	61	2013-06-11 04:30
Official "String copy Statement Considered Harmful" thread	Dubslow	Programming	19	2012-05-31 17:49

2018-03-21, 23:15	#1442
tha Dec 2002 5×163 Posts	mprime was set to use 2,5 GB of ram which is more than sufficient to run this exponent with this B1/B2 setting. Can someone try this on his/ her machine? Could it be that the known factors are used as settings that don't make sense? Or that the line in worktodo should be constructed differently?

2018-03-22, 14:07	#1448
tha Dec 2002 5·163 Posts	Also does not result in a start of stage2. Removing the known factors is the only way to start stage2, even with B2=12000000. However, we wanted to start the line with the known factors in place, to test if the server will accept the higher B1/B2 bounds for inclusion in the data available on the exponent.

2018-03-22, 14:34	#1449
error Sep 2014 23 Posts	Known factors should be put in between quotation marks: ...,"known,factors"