The range of k=8G-9G for n=25K-100K has been released.

[QUOTE=gd_barnes;400918]The range of k=8G-9G for n=25K-100K has been released.[/QUOTE]

I'm reserving this range (8G-9G), from n=25001 to n=100K. I'm using LLR 3.8.15 (64-bit Console version)

[QUOTE=KEP;404390]I'm reserving this range (8G-9G), from n=25001 to n=100K. I'm using LLR 3.8.15 (64-bit Console version)[/QUOTE]

How is the k=9G-13G for n=25K-100K reservation coming along? The last status was on Jan. 20th.

Question for future reference. How long does it take for a single AVX core to complete a range of 1G to 25K?

[QUOTE=gd_barnes;404415]How is the k=9G-13G for n=25K-100K reservation coming along? The last status was on Jan. 20th.[/QUOTE]

n=~86K (about 2.6M tests remaining and a test takes 7.3 seconds at this depth), ETA is late July on my Hasswell. The range 8G-9G is run on my Sandy Bridge, since I got a core freed up :smile:

For 9G-13G, a little less than 7970 k's remain.

Very good Kenneth. That's a lot of work!

[QUOTE=rogue;404418]Question for future reference. How long does it take for a single AVX core to complete a range of 1G to 25K?[/QUOTE]

You might try PMing Peter. All of my machines are older and fairly slow.

[QUOTE=gd_barnes;404447]Very good Kenneth. That's a lot of work![/QUOTE]

Thanks. Yes it is a lot of work :buddy:

[QUOTE=gd_barnes;404448]You might try PMing Peter. All of my machines are older and fairly slow.[/QUOTE]

Are you still running the Q6600s? Might be worth thinking about how long it would take to save money by getting the same throughput for less power consumption with new pcs.

[QUOTE=rogue;404418]Question for future reference. How long does it take for a single AVX core to complete a range of 1G to 25K?[/QUOTE]

On an Intel(R) Core(TM) i5-2300 CPU @2.8GHz it takes about 100 days to test a 1G range to n=2500 using -f0

This will leave about 75000 k's remaining per G, wich will have to be sieved and tested, but I think that such an approach will make you do a 1G range per core, in about 4 months total AVX CPU time.

Since I'm always using -f0 and n=2500 for b=3, I can't tell you how long it will take if you use -f30 (wich Gary has recommended in the past).

On a sidenote. I have begun working the range from:

k=40,000,000,002 to k=63,064,644,936

Here is the overall plan:

Step 1: Test all 11,532,322,468 k's to n=2500 using Starting base script with -f0 and using PFGW version 3.7.9
Step 2: Sieve remaining k's from n=2501 to n=7500 and test using PFGW version 3.7.9
Step 3: Sieve remaining k's from n=7501 to n=25000 and test using PFGW version 3.7.9

I expect step 1 to complete somewhere around February and afterwards that step 2 and 3 will complete in march and april 2016 (maybe sooner)

If Gary can accept this plan, he can make an official reservation, else I'll continue working this range with 3 sandy bridge cores (already running) and 4 hasswell cores (from around august 5th), without anything official noticed. However, even though noone else, besides Gary and I seems to be starting ranges for R3, then please try and remember this post, since I would hate wasting many months of work.

A final note, I have started testing these high k's to allow room for other people to search smaller ranges without me leaving a huge gap between completed ranges. Also I have thought this through :smile:

Now let's go kick some *** and finally achieve what I initially failed to achieve with "the Riesel base 3 attack" :smile:

Take care everyone

KEP

[QUOTE=KEP;405092]On an Intel(R) Core(TM) i5-2300 CPU @2.8GHz it takes about 100 days to test a 1G range to n=2500 using -f0

This will leave about 75000 k's remaining per G, wich will have to be sieved and tested, but I think that such an approach will make you do a 1G range per core, in about 4 months total AVX CPU time.

Since I'm always using -f0 and n=2500 for b=3, I can't tell you how long it will take if you use -f30 (wich Gary has recommended in the past).

On a sidenote. I have begun working the range from:

k=40,000,000,002 to k=63,064,644,936

Here is the overall plan:

Step 1: Test all 11,532,322,468 k's to n=2500 using Starting base script with -f0 and using PFGW version 3.7.9
Step 2: Sieve remaining k's from n=2501 to n=7500 and test using PFGW version 3.7.9
Step 3: Sieve remaining k's from n=7501 to n=25000 and test using PFGW version 3.7.9

I expect step 1 to complete somewhere around February and afterwards that step 2 and 3 will complete in march and april 2016 (maybe sooner)

If Gary can accept this plan, he can make an official reservation, else I'll continue working this range with 3 sandy bridge cores (already running) and 4 hasswell cores (from around august 5th), without anything official noticed. However, even though noone else, besides Gary and I seems to be starting ranges for R3, then please try and remember this post, since I would hate wasting many months of work.

A final note, I have started testing these high k's to allow room for other people to search smaller ranges without me leaving a huge gap between completed ranges. Also I have thought this through :smile:

Now let's go kick some *** and finally achieve what I initially failed to achieve with "the Riesel base 3 attack" :smile:

Take care everyone

KEP[/QUOTE]

If you want to finish it faster we could add some ranges into BOINC.