Reserving S917. It appears that it needs more sieving. srsieve2cl has already found three new factors for the range in less than an hour.

[QUOTE=rogue;589137]Reserving S917. It appears that it needs more sieving. srsieve2cl has already found three new factors for the range in less than an hour.[/QUOTE]

That base was not sent to Yoyo for additional sieving. Would you wait few days, I can put it for in front of remain bases, so it should be done quickly
Since our standard sieve depth for single sequence is 1e15 sieving should remove about 770 candidates or about 10.6% ( in whole sieve range up to 1M)

[QUOTE=pepi37;589144]That base was not sent to Yoyo for additional sieving. Would you wait few days, I can put it for in front of remain bases, so it should be done quickly
Since our standard sieve depth for single sequence is 1e15 sieving should remove about 770 candidates or about 10.6% ( in whole sieve range up to 1M)[/QUOTE]

I am sieving with srsieve2cl, which is faster than sr1sieve for this sequence. It doesn't bother me to sieve more deeply.

[QUOTE=rogue;589147]I am sieving with srsieve2cl, which is faster than sr1sieve for this sequence. It doesn't bother me to sieve more deeply.[/QUOTE]

Ok, as you wish 😊

[QUOTE=rogue;589147]I am sieving with srsieve2cl, which is faster than sr1sieve for this sequence. It doesn't bother me to sieve more deeply.[/QUOTE]

FYI, srsieve2cl is sieving at about 5x the speed of sr1sieve for this sequence. That calculation accounts for the difference in how p/sec is computed. I suspect the GPU is starving for work due to heavy CPU utilization when this is running.

S848 k=4 at 615K

Reserving S962 for n=250K-300K.

Reserving R567 to n=300k (200-300k) for BOINC

S908 tested to n=300k (200-300k)

1 prime found, 7 remain

Results emailed - Base released

R792 tested to n=300k (100-300k)

4 primes found, 7 remain

Results emailed - Base released

R1017 tested to n=300k (250-300k)

1 prime found, 5 remain

Results emailed - Base released