Sorry for double post - reserving R894 - note that I am only taking k = 6. Will go as far as to prove it hopefully.

Why don't you just continue with S991 and take it to n=50000? We're in no hurry.

In 15 days, I got 160 work units done. There were about 4,000 workunits in the initial batch - at that rate, I'd be done in a year. 25,000 to 50,000 would take about 4 years and two months.

That kind of timeframe is overdoing it for the first reservation I ever make. At the current rate i'm rolling now, I'll be at n=30k for k=6 in the next hour - n=100k in about 12 hours of wall clock time. That's a lot more achievable - I could do that this weekend.

[QUOTE=f1pokerspeed;311760]Sorry for double post - reserving R894 - note that I am only taking k = 6. Will go as far as to prove it hopefully.[/QUOTE]

Be sure and use the sieve file link on the Riesel reservations page. It is sieved for n=25K-100K to P=1T. You can quickly use the srfile program to remove all k's that are not = 6. Note that there are "only" 1074 tests for k=6 for this n-range and sieve depth. On a base of this size sieved that far for just one k, that gives you only about a 13-14% chance of finding a prime by n=100K. Therefore even testing all the way to n=100K where the tests can push a half hour each, the chances are small that you will find a prime.

Just figured I'd give you a heads up on the amount of CPU effort required on large bases here at CRUS.

[QUOTE=f1pokerspeed;311769]In 15 days, I got 160 work units done. There were about 4,000 workunits in the initial batch - at that rate, I'd be done in a year. 25,000 to 50,000 would take about 4 years and two months.

That kind of timeframe is overdoing it for the first reservation I ever make. At the current rate i'm rolling now, I'll be at n=30k for k=6 in the next hour - n=100k in about 12 hours of wall clock time. That's a lot more achievable - I could do that this weekend.[/QUOTE]

How many cores do you have? You might want to recheck those calculations for CPU time needed on k=6 for R894. See my previous post.

I have a quad-core laptop and a dual-core desktop. The laptop has AVX, but as a consequence of that it runs out of battery quickly.

I thought that a prime before n=100k might be possible

(NB: I extrapolated on the total testing time for a single core - oh well, it may be a couple of days then. Time to fire up the desktop...

[QUOTE=f1pokerspeed;311832]I have a quad-core laptop and a dual-core desktop. The laptop has AVX, but as a consequence of that it runs out of battery quickly.

I thought that a prime before n=100k might be possible

(NB: I extrapolated on the total testing time for a single core - oh well, it may be a couple of days then. Time to fire up the desktop...[/QUOTE]

I would suggest leaving the laptop plugged into an outlet and removing the battery. Then you have no worries about battery life. Also, the heat generated by the testing lowers the life of the battery quite a bit.

My estimate for k=6 n=25K-100K was around 15 CPU days. So yeah, 2-3 days if running 6 cores 24x7.

Reserving S640 (new, ck = 11925) to n=25k.
Reserving S642 (new, ck = 10932) to n=25k.

R653
 

R653 tested n=25K-100K - nothing found

6k's remain - Results emailed

S943
 

Reserving S943 as new to n=25K

R1027 is complete to n=25K.

122 primes found. Results have been emailed.