20090220, 09:03  #23 
Jun 2006
Chertsey Surrey UK
358_{10} Posts 
I will pick up the following ranges
4250G4500G 4750G5000G 5250G5500G 5750G6000G No ETA yet 
20090224, 10:42  #24 
May 2007
Kansas; USA
7^{2}·11·19 Posts 
Ian, Brian, and Chris, can you post an ETA on your sieve ranges? I'm going to put them in the 1st post of this thread. It'll help me determine if I need to put more and or can put less cores on the effort.
My current range will complete on Feb. 26th. Thanks, Gary Last fiddled with by gd_barnes on 20090224 at 10:44 
20090224, 11:30  #25 
May 2008
Wilmington, DE
2^{2}·23·31 Posts 
19th of Mar for me.

20090224, 14:14  #26 
I quite division it
"Chris"
Feb 2005
England
31×67 Posts 
ETA 3rd March.
(I'm still recovery from the disappointment of not finding 35 primes in one day.) Last fiddled with by Flatlander on 20090224 at 14:37 
20090225, 02:29  #27 
Jun 2006
Chertsey Surrey UK
358_{10} Posts 
5th Mar

20090225, 05:10  #28 
May 2007
Kansas; USA
10241_{10} Posts 
Thanks guys. I noted the ETA's in the 1st post of this thread.
Sometime on Feb. 26th, I'll reserve another P=3T range. Likely on March 14th15th, I'll get another P=3T range. I may reserve a little more on the 14th15th reservation depending on what others have reserved. I'm hoping that we can make P=15T by March 31st. Regardless, that is the day that we'll break off n=500K600K. If the 8th drive is done at that point, I'm taking Chris's advice and starting the 10th drive with that smaller nrange, even if we aren't quite sieved far enough. P=15T would be 3 times further sieved than the same nrange for the 1st drive so that's sufficient as far as I'm concerned. Gary 
20090225, 05:14  #29  
A Sunny Moo
Aug 2007
USA (GMT5)
1861_{16} Posts 
Quote:


20090225, 05:48  #30  
May 2007
Kansas; USA
7^{2}·11·19 Posts 
Quote:
Actually, no, I had planned on starting a new drive anyway for k=4001001, regardless of splitting the kranges, because n=320K1M would have been a huge range for 300 k's. Like with the 1st drive, even if we don't split the kranges for k=14002000, extending it to n=350K1M would make it too huge. There are two things to consider here: 1. We know that Benson will take k=10031400 to n=600K. Will he take that range for n>600K? I think he is but I need to ask specifically. 2. Do we want to take k=14002000 to n=600K and then split it into 3 kranges or keep it as one krange? My preference is one huge krange. Otherwise, we would have so many drives going, it would become unmanageable. Assuming that we keep k=14002000 as one huge krange up to n=1M and if Benson will be searching k=10032000 for n>600K, we should create a 10th drive for n=500K1M. Otherwise it's just too huge. If we decide to split it up into 3 kranges, we should extend the 8th drive to n=600K, and then create 10th/11th/12th drives for n=600K1M. One more caveat: If Benson is not going higher than n=600K, we should probably extend the 8th drive to n=600K, create a 10th drive for k=10031400/n=600K1M and an 11th drive for k=14002000/n=600K1M. I'd like to have them be different sizes like that so that they could progress at different rates, giving larger choices of nranges to search for people. Having one drive for 500 k's for n=600K1M would just be too big. We like to feel like we are completing large chunks of work. I think Karsten would scream if we did 3 more drives just for k=14002000, regardless of what Benson is doing with k=10031400 for n>600K. Also, I don't want to mess with so many different servers. Gary Last fiddled with by gd_barnes on 20090225 at 05:53 

20090225, 07:06  #31  
A Sunny Moo
Aug 2007
USA (GMT5)
79^{2} Posts 
Quote:


20090225, 09:17  #32 
I ♥ BOINC!
Oct 2002
Glendale, AZ. (USA)
3×7×53 Posts 
When are we recycling the drive numbers so they start over at drive 0 ?
Do we really have 10 drives going at once now? Last fiddled with by IronBits on 20090225 at 09:17 
20090225, 09:41  #33  
May 2007
Kansas; USA
24001_{8} Posts 
Quote:
No, drives 1 thru 4 are complete. Drives 5 thru 9 are ongoing so 5 "formal" drives that are run on servers. There is also the doublecheck drive and the individualk drive, neither of which are run on servers. The latter of those 2 drives also contains a subset called the "6k mini drive" that is an informal drive on just 6 k's running on my port 8000. There is also this sieving drive but that's not really a testing drive. Since the mini drive is a subset of the individualk drive, we have 7 full drives currently running (5 full drives on servers) plus this sieving drive. Drive 8 will finish and roll right into drive 10. It will be the same as when drive 1 finished and it rolled right into drives 5/6/7. This is the reason that I don't want any one drive to be too huge. I don't want to get 10 "formal" drives going at once. We'll feel like we're never completing anything. We also may get these temporary "fill in" thingies going at times like we've had on ports 2000 and 3000 but those should generally be small. Gary Last fiddled with by gd_barnes on 20090225 at 09:43 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Team drive #10 k=14002000 n=500K1M  gd_barnes  No Prime Left Behind  61  20130130 16:08 
Misc. reserves/statuses/primes for k>2000 & k=1003  gd_barnes  No Prime Left Behind  113  20090730 22:32 
Sieving drive for k=20003400 n=50K1M  gd_barnes  No Prime Left Behind  145  20090623 18:28 
Team drive #8 k=14002000 n=350K500K  gd_barnes  No Prime Left Behind  101  20090408 02:11 
Sieving drive for k=10052000 n=200K500K  gd_barnes  No Prime Left Behind  118  20090117 16:05 