mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   No Prime Left Behind (https://www.mersenneforum.org/forumdisplay.php?f=82)
-   -   PRPnet servers for NPLB (https://www.mersenneforum.org/showthread.php?t=12224)

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. :smile:

(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. :smile:

mdettweiler 2017-07-21 13:02

Port 9000 is empty now at n=1.5M. :smile:

(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=mdettweiler;463830]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. :smile:[/QUOTE]

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=odicin;463965]Hmm.. Not having any problems to connect on port 2000 on my side ;)[/QUOTE]
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=gd_barnes;463981]I will also try clearing out some old results from port 2000. Perhaps that will help.[/QUOTE]
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. :smile:

unconnected 2018-12-19 09:05

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

AMDave 2018-12-26 04:50

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


All times are UTC. The time now is 16:35.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.