reserving k=250e6-500e6 to n=100e3

[QUOTE=VBCurtis;300487]Taking 2000M to 2050M.[/QUOTE]

complete to n=100k. I'll gather the data together and email primes to Gary this week.
-Curtis

Gary has received the data, and informs me there were 682 k's left after testing to 10k, 73 after testing to 100k.

I am embarking on a sieve of the entire region 500M to 2000M from 25k to 100k. I certainly do not plan to test this range in its entirety, but I expect to have enough sieving complete by 1 Dec to share files with anyone interested in doing some primality testing for base 3.
-Curtis

The sieve is at 10G, roughly sufficient to test the lowest N values.
I am testing 25000 to 26000 now, expecting over 200 primes in that range.
26000 to 27000 should be ready 1 Oct when the sieve reaches 12G, if anyone is interested.
-Curtis

[QUOTE=VBCurtis;312444]The sieve is at 10G, roughly sufficient to test the lowest N values.
I am testing 25000 to 26000 now, expecting over 200 primes in that range.
26000 to 27000 should be ready 1 Oct when the sieve reaches 12G, if anyone is interested.
-Curtis[/QUOTE]

k=500M-2G is complete to n=26K. 276 k's were found prime for n=25K-26K. 7529 k's remain for the k-range.

I am showing k=500M-2G as reserved by you for testing to n=27K. Let me know if you plan differently.

k=500M to 2G complete to 27k. Primes sent to Gary.

Reserving 27k to 28k.

The sieve is complete to 16G, sufficient for tests to at least 30k if anyone wants to run a 1k block. Roughly 7250 k's remain in 500M to 2G.
-Curtis

[QUOTE=VBCurtis;314933]k=500M to 2G complete to 27k. Primes sent to Gary.

Reserving 27k to 28k.

The sieve is complete to 16G, sufficient for tests to at least 30k if anyone wants to run a 1k block. Roughly 7250 k's remain in 500M to 2G.
-Curtis[/QUOTE]

265 k's were found prime for n=26K-27K. 7264 k's remain for the k-range.

I do not recommend splitting up n-ranges on such a huge base. For the primes that you find for n=27K-28K, someone else would end up testing those same k's for n=28K-29K. If the range is to be split up, it's better to split by k's.

I suppose this depends on how much work someone wishes to take on. For a 1k block at a time, roughly 3% of the CPU time is wasted in overlap with redundant k's. On the other hand, CPU time is vastly cheaper than human-administrative time in splitting ranges by k, tracking which blocks have been split or not split, etc.

For a user taking a flier on a single 1k block, simplicity wins. If someone wants to do a CPU-month or more, I can split files by k while maintaining a single sieve. I also don't mind pausing my LLR work while someone else does a 1k block- this removes most inefficiency of the sort you observe.

Anyway, I welcome teamwork on this endeavor.

David (henryzz) has completed k=10M-20M to n=425K; 4 primes were found for n=250K-425K previously reported; the base is released.

r3
 

k = 250e6 - 500e6 complete to n=100e3.

859 primes.

results here: [URL]http://primes.ctrl-x-c.de/[/URL]

base released

Reserving 2050M to 2100M.

27k to 28k complete on 500M-2000M. Reserving 28k to 29k.
-Curtis