PRPnet servers for NPLB - Page 21

MyDogBuster · 2017-03-21, 21:28

Seems servers back up, grab what you need.

mdettweiler · 2017-07-20, 13:09

FYI @Gary: Port 9000 will dry out (at n=1.5M) in a few hours. I've had some fairly heavy resources on it for the last month which have managed to push it quite a bit farther than port 2000.

(I would've preferred to work on port 2000 since it's farther behind, but for some reason these particular computers have a hard time connecting to it. Something to do with it having a more heavily loaded database and taking longer for the server to respond to requests; for whatever reason, these clients are more sensitive to timeouts and 2000 can never respond fast enough. 9000 is just faster enough, apparently. Rather weird, since I've got a Windows box on a much worse Internet connection which has happily connected to 2000 for years...maybe there's a more aggressive firewall on the work boxes that's closing the connections quickly.)

I'm planning to move these boxes back to CRUS after 9000 gets to n=1.5M, but I'm sure the others on the port will appreciate some new work.

mdettweiler · 2017-07-21, 13:02

Port 9000 is empty now at n=1.5M.

(Gary, I don't have the sieve files on my end any more after a hard drive crash last year, so you're going to need to load this up on your end.)

odicin · 2017-07-22, 06:44

Quote:

Originally Posted by mdettweiler

I'm planning to move these boxes back to CRUS after 9000 gets to n=1.5M, but I'm sure the others on the port will appreciate some new work.

Hmm.. Not having any problems to connect on port 2000 on my side ;)

Regards Odi

gd_barnes · 2017-07-22, 15:14

OK. I will look to add some new work to port 9000 sometime late today or on Sunday.

I will also try clearing out some old results from port 2000. Perhaps that will help.

mdettweiler · 2017-07-22, 19:35

Quote:

Originally Posted by odicin

Hmm.. Not having any problems to connect on port 2000 on my side ;)

Yeah, it's just these particular boxes at work; none of my home boxes have a problem talking to port 2000. The best guess I can come up with is that perhaps the firewall at work is more aggressive about closing connections if they take too long to get through.

Are you running Windows, Linux, or Mac? My home boxes (which can connect fine) are running Windows but the work boxes run Linux. I'm wondering if that might be related to the difference (perhaps the Linux distro in use there - Fedora 24 - is configured to have stricter connection timeouts; but I would think that's something the PRPnet client would specify itself when making networking API calls, so it would seem strange for the OS to be the problem).

Quote:

Originally Posted by gd_barnes

I will also try clearing out some old results from port 2000. Perhaps that will help.

That would be great, thanks! Whatever's causing the specific problem I'm seeing, the huge amount of past results in port 2000 is almost certainly the root cause of why the server is (by far) the slowest to respond of all our servers.

9000 could also use some cleaning out too (especially with new work being loaded) - it's no speed demon either.

gd_barnes · 2017-07-22, 22:19

Both ports 2000 and 9000 have now been loaded with work up to n=1.6M.

I copied off and then deleted all primes and results for n<=1.5M from port 9000 and for n<=1.4M from port 2000.

That should help things out a little.

unconnected · 2018-12-19, 09:05

JFYI, NPLB stats are not updated at Free-DC anymore.
https://stats.free-dc.org/users/nplb

AMDave · 2018-12-26, 04:50

Thanks.
Looks like the individual scores only.
Team scores are still updating.
I'll check with Bok.

gd_barnes · 2022-02-20, 06:32

Ports 2000 and 9000 are barely out of the top-5000 range at the moment but they could make it back into top-5000 at any time.

If anyone here (namely Dmitry or Tim) sees a prime of mine on the ports before I do they are welcome to report it to the top-5000 site as their own. Who gets credit doesn't concern me. We'd just like to get the primes reported there if possible.

gd_barnes · 2022-02-21, 06:42

We are back in top-5000 range. Current leading edge is at place 4995 for both ports 2000 and 9000.

Only PrimeGrid's Mountain Stage dropped us below for about a day. We should be good now but keep it up through the first week in March. :-)

2017-07-20, 13:09	#222
mdettweiler A Sunny Moo Aug 2007 USA (GMT-5) 3·2,083 Posts	FYI @Gary: Port 9000 will dry out (at n=1.5M) in a few hours. I've had some fairly heavy resources on it for the last month which have managed to push it quite a bit farther than port 2000. (I would've preferred to work on port 2000 since it's farther behind, but for some reason these particular computers have a hard time connecting to it. Something to do with it having a more heavily loaded database and taking longer for the server to respond to requests; for whatever reason, these clients are more sensitive to timeouts and 2000 can never respond fast enough. 9000 is just faster enough, apparently. Rather weird, since I've got a Windows box on a much worse Internet connection which has happily connected to 2000 for years...maybe there's a more aggressive firewall on the work boxes that's closing the connections quickly.) I'm planning to move these boxes back to CRUS after 9000 gets to n=1.5M, but I'm sure the others on the port will appreciate some new work. Last fiddled with by mdettweiler on 2017-07-20 at 13:10

2017-07-21, 13:02	#223
mdettweiler A Sunny Moo Aug 2007 USA (GMT-5) 3·2,083 Posts	Port 9000 is empty now at n=1.5M. (Gary, I don't have the sieve files on my end any more after a hard drive crash last year, so you're going to need to load this up on your end.) Last fiddled with by mdettweiler on 2017-07-21 at 13:03

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PRPnet Servers for CRUS	MyDogBuster	Conjectures 'R Us	83	2021-01-28 10:08
LLRnet servers for NPLB	kar_bon	No Prime Left Behind	1343	2014-08-20 09:38
Public PRPNet Servers	rogue	Open Projects	26	2013-01-16 01:33
PRPNet servers down?	opyrt	Prime Sierpinski Project	13	2009-11-04 21:33
Servers for NPLB	gd_barnes	No Prime Left Behind	0	2009-08-10 19:21

2017-03-21, 21:28	#221
MyDogBuster May 2008 Wilmington, DE 101100100100₂ Posts	Seems servers back up, grab what you need.

2017-07-22, 15:14	#225
gd_barnes "Gary" May 2007 Overland Park, KS 13×907 Posts	OK. I will look to add some new work to port 9000 sometime late today or on Sunday. I will also try clearing out some old results from port 2000. Perhaps that will help.

2017-07-22, 22:19	#227
gd_barnes "Gary" May 2007 Overland Park, KS 13·907 Posts	Both ports 2000 and 9000 have now been loaded with work up to n=1.6M. I copied off and then deleted all primes and results for n<=1.5M from port 9000 and for n<=1.4M from port 2000. That should help things out a little.

2018-12-19, 09:05	#228
unconnected May 2009 Moscow, Russia 2³×19² Posts	JFYI, NPLB stats are not updated at Free-DC anymore. https://stats.free-dc.org/users/nplb

2018-12-26, 04:50	#229
AMDave Jan 2006 deep in a while-loop 2²·167 Posts	Thanks. Looks like the individual scores only. Team scores are still updating. I'll check with Bok.

2022-02-20, 06:32	#230
gd_barnes "Gary" May 2007 Overland Park, KS 13×907 Posts	Ports 2000 and 9000 are barely out of the top-5000 range at the moment but they could make it back into top-5000 at any time. If anyone here (namely Dmitry or Tim) sees a prime of mine on the ports before I do they are welcome to report it to the top-5000 site as their own. Who gets credit doesn't concern me. We'd just like to get the primes reported there if possible.

2022-02-21, 06:42	#231
gd_barnes "Gary" May 2007 Overland Park, KS 27017₈ Posts	We are back in top-5000 range. Current leading edge is at place 4995 for both ports 2000 and 9000. Only PrimeGrid's Mountain Stage dropped us below for about a day. We should be good now but keep it up through the first week in March. :-)