Bases 6-32 reservations/statuses/primes

[rogue]

Originally Posted by lalera

i meant the lines with the phase=

Read the document pfgwdoc.txt for usage of the -Bspec switch. When you see the output, it should tell you where the FFT crossovers are. Use those crosovers as the high end of each phase. Larger b (than base 3) will require deeper sieving. You can use the timing for the PRP test output by pfgw with the -Bspec switch and do some testing with srsieve to get removal rates similar to the time for individual tests. For example, if -Bspec indicates that a test takes 2 seconds, then for the candidates input into srsieve, you want a removal rate of about 1 per 2 seconds and that will establish your sieve depth. I don't have time to run through an example of this, but I know that others reading this could do so.

[lalera]

Originally Posted by rogue

Read the document pfgwdoc.txt for usage of the -Bspec switch. When you see the output, it should tell you where the FFT crossovers are. Use those crosovers as the high end of each phase. Larger b (than base 3) will require deeper sieving. You can use the timing for the PRP test output by pfgw with the -Bspec switch and do some testing with srsieve to get removal rates similar to the time for individual tests. For example, if -Bspec indicates that a test takes 2 seconds, then for the candidates input into srsieve, you want a removal rate of about 1 per 2 seconds and that will establish your sieve depth. I don't have time to run through an example of this, but I know that others reading this could do so.

thank you !

[lalera]

hi,
i did the following ranges
on a sbe3930k - 6 concurrent tasks
with srbsieve v4 for windows and the standard srbsieve.ini
newpgen to n=17 | n= to 25k
R7k110M120M - 80:04:21 - 185 remaining
R7k120M130M - 86:34:43 - 208 remaining
R7k130M140M - 84:20:09 - 192 remaining
R7k140M150M - 85:32:05 - 211 remaining
R7k150M160M - 87:20:11 - 198 remaining
R7k160M170M - 83:59:35 - 195 remaining

you can download the complete results
from my shared folder at google drive
rieselbase7

[lalera]

i completed the range
S15; k<=5m; n=100k-150k
no prime
10 k´s remaining
results emailed
base released

[lalera]

hi,
i did the following ranges
on a sbe3930k
with srbsieve v4 for windows and the standard srbsieve.ini
R7; k=110M-200M; n=1-25k
newpgen to n=17
R7k110M120M - 80:04:21 - 185 remaining
R7k120M130M - 86:34:43 - 208 remaining
R7k130M140M - 84:20:09 - 192 remaining
R7k140M150M - 85:32:05 - 211 remaining
R7k150M160M - 87:20:11 - 198 remaining
R7k160M170M - 83:59:35 - 195 remaining
R7k170M180M - 81:21:59 - 185 remaining
R7k180M190M - 84:22:19 - 180 remaining
R7k190M200M - 79:56:20 - 181 remaining

total 1735 remaining k´s

you can download the complete results
from my shared folder at google drive
rieselbase7
results emailed
range released

[rebirther]

R27 tested to n=2M (1.5-2M)

nothing found

Results emailed, Base released

[lalera]

hi,
i did the following range
with srbsieve v5 for windows
R7; k=200M-500M; n=1-25k
6099 k´s remaining
results emailed
base released

you can download the complete results
from my shared folder at google drive
rieselbase7

[rogue]

Originally Posted by lalera

hi,
i did the following range
with srbsieve v5 for windows
R7; k=200M-500M; n=1-25k
6099 k´s remaining
results emailed
base released

you can download the complete results
from my shared folder at google drive
rieselbase7

How long did it take?

[lalera]

i did it on 2 machines with different loads
one sbe3930k and one Xeon 2630 v3 - both running windows10
the timings maybe are not representative
if you like you can download the complete results from my shared folder at google drive
look at the "xxxscreen.txt" files

[Cruelty]

S10 tested till n=1.59M
R10 tested till n=1.39M

[Cruelty]

S10 tested till n=1.63M
R10 tested till n=1.43M