Gaps to close

ET_ · 2017-11-14, 21:23

Here are the current gaps:

Code:

6151-6199 1000000000 2500000000
6201-6299 900000000 1000000000                  
6301-6399 800000000 900000000              reserved
10003-10999 100000000 269000000 
14501-14999 40000000 70000000
181744-189999 13000 30000                  reserved

Mark and I will try to keep up with such reservations.

rogue · 2017-11-15, 14:15

It turns out that fermfact can not handle overly large ranges of k. That's annoying.

rogue · 2017-11-15, 16:30

Here are some updates:

Code:

6151-6199 1000000000 2500000000
6201-6299 900000000 1000000000             rogue sieving
6301-6399 800000000 900000000              reserved by Adolf Nordin
10003-10999 100000000 269000000            rogue sieving
14501-14999 40000000 70000000              wombatman sieving, rogue to test
181744-189999 13000 30000                  reserved by Frederick Hermanns

rogue · 2018-02-15, 16:57

[QUOTE=rogue;471883]Here are some updates:

Code:

6201-6299 900000000 1000000000             lost sieve data, will start resieving soon
10003-10999 100000000 269000000            lost sieve data, resieving (by me)
14501-14999 40000000 70000000              testing in progress (by me)

That range for 10003-10999 had around 84e9 terms when sieving started. It is down to about 3.5e9 terms after two days of sieving with gfndsieve. Using the single-threaded version, I have 6 copies going with about 160 n per copy. Each is at about 7e12 and the removal rate is about 350 terms per second. I need to get to a rate of 20 terms removed per second. I don't know how many more days I will need to sieve but it will much deeper than fermfact, where I stopped at about 12e12 after about 10 days of sieving.

ET_ · 2018-02-16, 10:37

Quote:

Originally Posted by rogue

I don't know how many more days I will need to sieve but it will much deeper than fermfact, where I stopped at about 12e12 after about 10 days of sieving.

wombatman · 2018-02-16, 14:09

Just a heads-up. I'm sieving the 6151-6199 gap to 1e14 with gfndsieve (single-thread). ETA is current Feb. 26th, but that may come down as more numbers are removed and the sieving can speed up. We'll see how many factors are left at that point.

rogue · 2018-02-16, 15:51

Quote:

Originally Posted by wombatman

Just a heads-up. I'm sieving the 6151-6199 gap to 1e14 with gfndsieve (single-thread). ETA is current Feb. 26th, but that may come down as more numbers are removed and the sieving can speed up. We'll see how many factors are left at that point.

That means that you started with just under 37e9 terms.

wombatman · 2018-02-16, 16:29

Something like that, yes. Somewhere north of 35e9 terms have been removed (probably closer to 36e9 by now).

rogue · 2018-02-25, 01:15

Here are some updates:

Code:

6201-6299 900000000 1000000000    testing in progress, should be done in about 1 week
10003-10999 100000000 269000000   sieve on 6 cores
14501-14999 40000000 70000000     testing in progress should be done in about 2 weeks

The sieving for that range is at about 9e13 and removal rate is about twice as fast as a PRP test. I split across six cores because the multi-threaded gfndsieve wasn't working correctly at the time. Each core is sieving about 160 n. When sieving is done, I'll let you know how many tests there are and when I expect to finish the range.

rogue · 2018-03-01, 00:32

That one range is finally done sieving. I stopped at about 1.4e14. There are about 2.8e9 candidates remaining (after starting with about 87e9 candidates). If I put all of my resources against this, I estimate about 40 days of testing (30 tests per second per core).

rogue · 2018-03-01, 13:37

Quote:

Originally Posted by rogue

That one range is finally done sieving. I stopped at about 1.4e14. There are about 2.8e9 candidates remaining (after starting with about 87e9 candidates). If I put all of my resources against this, I estimate about 40 days of testing (30 tests per second per core).

That estimate is a little low as some cores are slower than others. I'm aiming to complete by the end of April.

2017-11-14, 21:23	#1
ET_ Banned "Luigi" Aug 2002 Team Italia 11371₈ Posts	Gaps to close Here are the current gaps: Code: 6151-6199 1000000000 2500000000 6201-6299 900000000 1000000000 6301-6399 800000000 900000000 reserved 10003-10999 100000000 269000000 14501-14999 40000000 70000000 181744-189999 13000 30000 reserved Mark and I will try to keep up with such reservations.

2018-02-15, 16:57	#4
rogue "Mark" Apr 2003 Between here and the 1B3B₁₆ Posts	[QUOTE=rogue;471883]Here are some updates: Code: 6201-6299 900000000 1000000000 lost sieve data, will start resieving soon 10003-10999 100000000 269000000 lost sieve data, resieving (by me) 14501-14999 40000000 70000000 testing in progress (by me) That range for 10003-10999 had around 84e9 terms when sieving started. It is down to about 3.5e9 terms after two days of sieving with gfndsieve. Using the single-threaded version, I have 6 copies going with about 160 n per copy. Each is at about 7e12 and the removal rate is about 350 terms per second. I need to get to a rate of 20 terms removed per second. I don't know how many more days I will need to sieve but it will much deeper than fermfact, where I stopped at about 12e12 after about 10 days of sieving. Last fiddled with by rogue on 2018-02-15 at 16:58

2018-02-25, 01:15	#9
rogue "Mark" Apr 2003 Between here and the 6,971 Posts	Here are some updates: Code: 6201-6299 900000000 1000000000 testing in progress, should be done in about 1 week 10003-10999 100000000 269000000 sieve on 6 cores 14501-14999 40000000 70000000 testing in progress should be done in about 2 weeks The sieving for that range is at about 9e13 and removal rate is about twice as fast as a PRP test. I split across six cores because the multi-threaded gfndsieve wasn't working correctly at the time. Each core is sieving about 160 n. When sieving is done, I'll let you know how many tests there are and when I expect to finish the range.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Large Gaps >500,000	mart_r	Prime Gap Searches	119	2017-08-21 12:48
Medium Gaps 60,000 to 500,000	robert44444uk	Prime Gap Searches	77	2016-12-28 08:19
Very small gaps - 1,300 - 4,000	robert44444uk	Prime Gap Searches	33	2016-02-03 12:55
Gaps and more gaps on <300 site	gd_barnes	Riesel Prime Search	11	2007-06-27 04:12
Are M41,42,43 too close to each other?	nngs	Lounge	12	2005-12-24 13:25

2017-11-15, 14:15	#2
rogue "Mark" Apr 2003 Between here and the 6,971 Posts	It turns out that fermfact can not handle overly large ranges of k. That's annoying.

2018-02-16, 14:09	#6
wombatman I moo ablest echo power! May 2013 2²×463 Posts	Just a heads-up. I'm sieving the 6151-6199 gap to 1e14 with gfndsieve (single-thread). ETA is current Feb. 26th, but that may come down as more numbers are removed and the sieving can speed up. We'll see how many factors are left at that point.

2018-02-16, 16:29	#8
wombatman I moo ablest echo power! May 2013 2²×463 Posts	Something like that, yes. Somewhere north of 35e9 terms have been removed (probably closer to 36e9 by now).

2018-03-01, 00:32	#10
rogue "Mark" Apr 2003 Between here and the 6,971 Posts	That one range is finally done sieving. I stopped at about 1.4e14. There are about 2.8e9 candidates remaining (after starting with about 87e9 candidates). If I put all of my resources against this, I estimate about 40 days of testing (30 tests per second per core).