LLRnet/PRPnet rally August 12th-19th

[kar_bon]

PRPnet Port 9000 is working again!

The last pair before the issue was submitted on 2010-08-15 02:28:21 and the first after than at 2010-08-15 06:11:37, so about 3h 43m offline.

[rogue]

Originally Posted by gd_barnes

Max and Mark, it's in your hands to see why this keeps happening. This is extremely frustrating in the middle of an otherwise successful rally.

I intend to look at it tomorrow. I might need to rely on Max to add some additional tracing, but we'll see. Max, if you can zip and e-mail me the log, I would appreciate it.

[vaughan]

Originally Posted by gd_barnes

I guess it all depends on whether you want to equal my TOTAL output for the entire week or just my hourly output -or- if you want an amount that will allow AMD users to overtake ROLP.

Bring it on!

Well I intended to match your hourly output on Port=3000 however ... I had some network issues that required a re-boot of my local server. I dropped production for a few hours as half my network couldn't get any work. All fixed now, I hope.

Challenge on.

[gd_barnes]

Originally Posted by vaughan

Aw come on Vato its not that bad! I'm running it on at least two dozen cores because I just don't understand how to setup the newfangled PRPnet thingy with its do.bat and so on.

??

PRPnet has nothing to do with do.bat. That's the new LLRnet! Vaughan, have you been using the new LLRnet upgraded by Karsten many months ago? If you're still using the old version, you're losing nearly 10% in speed. You just download his files to your machines, change the config file to the correct userid and port, go to a command prompt, and type "do". When you want to stop, you just hit Ctl-C. It's very simple.

Vato, were you aware that we (mainly kar_bon) made changes to LLRnet so that it uses the latest version of LLR? It's as fast as PRPnet.

I'm not trying to push people one way or another at this point. I just want to offer the choice, make sure everyone has the facts straight, and let people know how easy the latest versions of both LLRnet and PRPnet are to run clients on now. PRPnet is more difficult to set up and run personal servers but they are equally easy to run clients on. I use both for different things. PRPnet is generally better for longer tests and LLRnet is generally better for very short tests.


Gary

[gd_barnes]

Originally Posted by rogue

I intend to look at it tomorrow. I might need to rely on Max to add some additional tracing, but we'll see. Max, if you can zip and e-mail me the log, I would appreciate it.

It seems to happen about once per day with the heavy load from the rally. I think what I'll do now is manually stop and start the server 1-2 times per day. Perhaps something just needs to be cleared out from time to time with a heavy load.

...anything to avoid the max connections issue in the middle of the night like that.

[vaughan]

I'm using the old LLRnet client on all but one machine ... 10 percent faster, hey!

[gd_barnes]

Originally Posted by vaughan

I'm using the old LLRnet client on all but one machine ... 10 percent faster, hey!

Huh??

The OLD LLRnet client is 10% SLOWER!

You need the NEWER do.bat LLRnet client to get the 10% speed increase so that the clients run at the same speed as PRPnet.

I would suggest deleting all of that old LLRnet client junk. It's running LLR version 3.6.1. The latest LLRnet version is running LLR 3.8.1. That's what you need for the speed increase.

If you would like a care package sent to you with the new client, Max is quite adept at putting those together for people.

(caps for emphasis)

[gd_barnes]

I'm keeping an eye on things as much as I can. For the time being I'm going to stop and restart the PRPnet server and rename the prplog file twice per day: Once before I go to bed and once a couple of hours after I get up. I'll do these tasks approximately around 3AM and 2PM CDT U.S. each day. (8AM and 7PM GMT)

There should be little noticeable affect by the stopping and restarting. I hit ctl-C to stop it, wait 5 seconds, and then restart with the prpserver command.

It's been consistent enough both on the last rally and this rally that it would have a problem almost right at once per day that I'm hoping this will completely stop or reduce the problem dramatically.

[mdettweiler]

Originally Posted by gd_barnes

Huh??

The OLD LLRnet client is 10% SLOWER!

You need the NEWER do.bat LLRnet client to get the 10% speed increase so that the clients run at the same speed as PRPnet.

I would suggest deleting all of that old LLRnet client junk. It's running LLR version 3.6.1. The latest LLRnet version is running LLR 3.8.1. That's what you need for the speed increase.

If you would like a care package sent to you with the new client, Max is quite adept at putting those together for people.

(caps for emphasis)

I think that's what vaughan was saying, just in a different way...

BTW, the old LLRnet is based on 3.5.0, not 3.6.1. (At least the version that I've seen everywhere is. Heck, if it was based on 3.6.1, it would at least be as fast as 3.7.1c--there were no speed changes between those versions. 3.6.0 was about 6% faster than 3.5.0, and 3.8.0 added another 4%, for a total of 10%.)

[vaughan]

Maybe I'm a bit slow on the uptake of this but from what I've seen the 3.8 version 073 client for Windows with the hierarchical structure of LLRnet_server and LLRnet_client sub-directories and the do.bat file in the client one leads to fugly dos boxes on the screen.

Maybe I haven't followed the setup routine correctly but then I had enough problems getting my old head around setting up the LLRnet client I'm using now.

What I like about the prehistoric version I'm running is the GUI where I can quickly see the tasks that are crunching on each core, the total list of all cores cached tasks and the completed tasks (with primes at the top of the list {if any}).

[gd_barnes]

Originally Posted by vaughan

Maybe I'm a bit slow on the uptake of this but from what I've seen the 3.8 version 073 client for Windows with the hierarchical structure of LLRnet_server and LLRnet_client sub-directories and the do.bat file in the client one leads to fugly dos boxes on the screen.

Maybe I haven't followed the setup routine correctly but then I had enough problems getting my old head around setting up the LLRnet client I'm using now.

What I like about the prehistoric version I'm running is the GUI where I can quickly see the tasks that are crunching on each core, the total list of all cores cached tasks and the completed tasks (with primes at the top of the list {if any}).

I see what you mean now. Yeah, sorry, no GUI with the new LLRnet or with PRPnet. Just DOS boxes on the screen.

Karsten, was there ever any attempt to update the Windows GUI so that it works with the new LLRnet? I'm sure that would be a large undertaking.

In the mean time, I've just done my twice daily stop and restart of the PRPnet server before going to bed. Hopefully there will be no problems tonight/this morning.