[quote=IronBits;156466]Where is the :roflmao: icon when you need it?
prune period was fine, the variable I was using to print was not accurate ;)

Port [B]8000[/B] has 207657 remaining knpairs!
knpairs.txt - Size: 2491908
Last Updated: 1/2/2009 10:32:36 AM
first k/n pair 1945 350595
last k/n pair 1955 210000
jobMaxTime = 1 * 24 * 3600 -- 1 days
prunePeriod = 1 * 1 * 3600 -- hourly[/quote]
Ah, I *thought* that a prunePeriod of 1 day seemed a little odd based on what I'd observed from the server. :wink:

IB8000 seems to be coping with 40 second tests

[quote=henryzz;156508]IB8000 seems to be coping with 40 second tests[/quote]

Those tests won't give Top 5000 primes..:glare:

[quote=em99010pepe;156509]Those tests won't give Top 5000 primes..:glare:[/quote]
lets hope they get us out of our prime barrenness spell though
one new prime for 350k-352k was rubbish

[quote=em99010pepe;156509]Those tests won't give Top 5000 primes..:glare:[/quote]
Well, they should at least hold the server over until we've got some more top-5000 work for n>352K available later this month. :smile:

Indeed! It's doing just fine. :smile:
I broke 1,000 per hour mark, and I have 8 more cores coming soon to dry it out. :grin:

[quote=mdettweiler;156443]Hmm...Gary didn't reply to my query over in the Drive #8 thread about loading work starting at 200K into the server (maybe it got lost in all the other replies there?), but since time is of the essence I'll go ahead and send you 200K-210K shortly; that should keep port 8000 going for a reasonable amount of time. :smile:

In the meantime, we should report any primes found in this range in the Drive #8 thread, though when Gary sees this he can decided if we should keep track of the lower range in a new team drive.[/quote]

I hope this was appropriately responded to now. The reason why I wasn't concerned with loading anything more in port 8000 is because it was supposed to dry out and have everyone else move back to the other efforts.

Had I been concerned with it, I would have said something at 5 AM this morning (Vegas time; 1 PM GMT) when I was on previously because it was clear it would dry before I got back on again.

I guess that wasn't sufficiently communicated ahead of time. Sorry about the problems that it has caused.


Gary

David,

I figured I'd better be specific:

1. Please stop port 8000.

2. Please remove all k/n pairs that Max last sent you from knpairs.txt and any other files. These would include all pairs with an n-value (that is the 2nd value on each line) that is in the 200000-210000 range.

3. Restart port 8000.

4. Everyone please move cores to the sieving drive (highest priority), port 400 (higher priority port) or ports IB5000, G4000, or C6000.


Restarting the port will allow straggling k/n pairs to be processed within a day. If they don't, it means no one has connected after they were returned to the server. I'll make sure that they are all processed sometime on Saturday. If they haven't been, I'll connect and get them processed.


Thanks,
Gary

Grow up Gary. Let that range be on the server.

[quote=em99010pepe;156569]Grow up Gary. Let that range be on the server.[/quote]
Carlos, I'm afraid that after reviewing the situation, it looks like it will indeed be too messy and troublesome to manage that range. Remember, Gary has to verify all these ranges after we're done with them to see if they match up with the original sieve file, and it would be a *huge* pain in the butt to have to compare some portions with one sieve file and others with another. Not to mention that it increases the chances of errors being introduced into the range.

Thus, I am inclined to agree with Gary that the wisest move at this time is to hold off on processing 200K-210K. We really need to wait until sieving is complete for that range, and then start the range properly so that there are no confusing mix-ups.

Port 8000 is down.
I have no clue what you want me to do from here.
Talk to me in email, if you want me to turn port 8000 back on.
I'm pretty sure what ever it was supposed to finish, finished at around 3pm Arizona time.