LLRnet server rally port 300 May 3rd-4th

gd_barnes · 2008-05-02, 20:28

We would like to run a 24-hour LLRnet server rally on port 300 from May 3rd at 7 PM GMT to May 4th at 7 PM GMT.

This would be noon Sat.-noon Sun. PDT, 2 PM-2PM CDT, or 3 PM-3 PM EDT in the U.S.

Here is the server info.:
server = "nplb.rieselprime.org"
port = 300

General info. on setting up a connection to an LLRnet server can be found here. The above info. should be put in the llr-clientconfig.txt file.

Everyone bring all of your firepower to the rally as we see how fast we can bring drive 1 up to n=425K!

Gary

TimSorbet · 2008-05-02, 21:16

Ready to rumble.

The rally starts right when my brother's birthday party does, so we'll probably be doing some gaming (GH3 with custom songs) on it and so I'll be slowed for a while...I'll leave it on LLRNet work long enough to get in 24 CPU hours per core to compensate.

gd_barnes · 2008-05-02, 21:22

I'm bringing 2 quads plus at least 2 more cores to the rally so all of you heavy-hitters, bring it on!

Edit: Which reminds me, I need to get those Linux machines loaded up with LLRnet here shortly. Ah...more Linux learning curve. Fortunately Anon was kind enough to forward me some detailed instructions while I'm gone.

mdettweiler · 2008-05-03, 01:57

Gary, you need to make a note in the first post of this thread that the server is "nplb.rieselprime.org", since if people follow the instructions you linked to with port 300, they'll be trying to access Carlos's now-defunct port 300 server.

In other news, I'll bring two cores of a Core 2 Duo 2.2Ghz to the rally.

mdettweiler · 2008-05-03, 02:16

Oh, one more thing: I'll get some more knpairs put together for Adam to add to the port 300 server, since we'll want it to be fully loaded for the rally.

gd_barnes · 2008-05-03, 02:35

Quote:

Originally Posted by Anonymous

Gary, you need to make a note in the first post of this thread that the server is "nplb.rieselprime.org", since if people follow the instructions you linked to with port 300, they'll be trying to access Carlos's now-defunct port 300 server.

In other news, I'll bring two cores of a Core 2 Duo 2.2Ghz to the rally.

Specific server info. has now been added.

AES · 2008-05-03, 03:54

Please keep in mind that this is a Windows server and if a proxy is used (proxyMasterAddress), it will eventually stop releasing sockets and seize up.

Also, if you would like an email notification of new primes found, please send the email address and user name to Anon or AES.

mdettweiler · 2008-05-03, 04:11

Quote:

Originally Posted by AES

Please keep in mind that this is a Windows server and if a proxy is used (proxyMasterAddress), it will eventually stop releasing sockets and seize up.

Also, if you would like an email notification of new primes found, please send the email address and user name to Anon or AES.

So you're saying that personal proxies bog down the Windows servers? In that case, should users try to avoid using personal proxies on your server? It would mean more load on your network, but that's better than having the server lock up.

What you might want to consider is to install Virtual PC, VMware Player or some other free virtualization software on your Windows server machine, run a Linux/Unix variant in a VM, and run the LLRnet server from there. IronBits has reported that the Linux server is without a lot of the Windows server's idiosyncracies, so it might be quite beneficial to run it instead.

AES · 2008-05-03, 05:01

It doesn't really bog the server down or cause excess cpu/disk usage, it just causes it to stop releasing sockets and seize up for some reason. We've observed this on all Win32 servers we've set up. I don't know if llrnet clients alone will cause this.

The network traffic is negligible either way.

em99010pepe · 2008-05-03, 13:09

Quote:

Originally Posted by gd_barnes

I'm bringing 2 quads plus at least 2 more cores to the rally so all of you heavy-hitters, bring it on!

I think you should bring everything....added 6 cores to the fun.

Carlos

gd_barnes · 2008-05-03, 14:10

Quote:

Originally Posted by AES

It doesn't really bog the server down or cause excess cpu/disk usage, it just causes it to stop releasing sockets and seize up for some reason. We've observed this on all Win32 servers we've set up. I don't know if llrnet clients alone will cause this.

The network traffic is negligible either way.

Adam,

How is your server currently responding to things? I've had the full gammit of my machines that I'll have for the rally on port 300 for about 8 hours now. I'm not sure if Carlos has moved his 6 cores to it yet.

Do we need to encourage everyone to move all their machines at least an hour before the rally to make sure your server can handle it?

I'm going back to bed now...will be back on in ~3 hours.

Gary

2008-05-02, 20:28	#1
gd_barnes "Gary" May 2007 Overland Park, KS 2²·3,041 Posts	LLRnet server rally port 300 May 3rd-4th We would like to run a 24-hour LLRnet server rally on port 300 from May 3rd at 7 PM GMT to May 4th at 7 PM GMT. This would be noon Sat.-noon Sun. PDT, 2 PM-2PM CDT, or 3 PM-3 PM EDT in the U.S. Here is the server info.: server = "nplb.rieselprime.org" port = 300 General info. on setting up a connection to an LLRnet server can be found here. The above info. should be put in the llr-clientconfig.txt file. Everyone bring all of your firepower to the rally as we see how fast we can bring drive 1 up to n=425K! Gary Last fiddled with by gd_barnes on 2008-05-03 at 02:43

2008-05-02, 21:22	#3
gd_barnes "Gary" May 2007 Overland Park, KS 2²·3,041 Posts	I'm bringing 2 quads plus at least 2 more cores to the rally so all of you heavy-hitters, bring it on! Edit: Which reminds me, I need to get those Linux machines loaded up with LLRnet here shortly. Ah...more Linux learning curve. Fortunately Anon was kind enough to forward me some detailed instructions while I'm gone. Last fiddled with by gd_barnes on 2008-05-02 at 21:23

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
LLRnet server rally 400<k<1001 August 8-10	mdettweiler	No Prime Left Behind	66	2008-08-11 03:00
LLRnet server rally 400<k<1001 June 20-22	mdettweiler	No Prime Left Behind	67	2008-06-23 15:32
LLRnet server rally port 300 May 23rd-25th	gd_barnes	No Prime Left Behind	172	2008-06-04 19:21
priority for LLRnet port 8000!	IronBits	No Prime Left Behind	10	2008-04-17 10:09
LLRnet server rally March 8th-9th	gd_barnes	No Prime Left Behind	135	2008-03-14 19:52

2008-05-02, 21:16	#2
TimSorbet Account Deleted "Tim Sorbera" Aug 2006 San Antonio, TX USA 11×389 Posts	Ready to rumble. The rally starts right when my brother's birthday party does, so we'll probably be doing some gaming (GH3 with custom songs) on it and so I'll be slowed for a while...I'll leave it on LLRNet work long enough to get in 24 CPU hours per core to compensate.

2008-05-03, 01:57	#4
mdettweiler A Sunny Moo Aug 2007 USA 1894₁₆ Posts	Gary, you need to make a note in the first post of this thread that the server is "nplb.rieselprime.org", since if people follow the instructions you linked to with port 300, they'll be trying to access Carlos's now-defunct port 300 server. In other news, I'll bring two cores of a Core 2 Duo 2.2Ghz to the rally.

2008-05-03, 02:16	#5
mdettweiler A Sunny Moo Aug 2007 USA 6292₁₀ Posts	Oh, one more thing: I'll get some more knpairs put together for Adam to add to the port 300 server, since we'll want it to be fully loaded for the rally.

2008-05-03, 03:54	#7
AES Jul 2007 Tennessee 2⁵·19 Posts	Please keep in mind that this is a Windows server and if a proxy is used (proxyMasterAddress), it will eventually stop releasing sockets and seize up. Also, if you would like an email notification of new primes found, please send the email address and user name to Anon or AES.

2008-05-03, 05:01	#9
AES Jul 2007 Tennessee 2⁵×19 Posts	It doesn't really bog the server down or cause excess cpu/disk usage, it just causes it to stop releasing sockets and seize up for some reason. We've observed this on all Win32 servers we've set up. I don't know if llrnet clients alone will cause this. The network traffic is negligible either way.