LLRnet rally Apr. 30th to May 2nd

[gd_barnes]

Hi everyone,

I'd like to announce NPLB first LLRnet rally in over a year! The rally will begin on Friday, April 30th at 7:00 PM GMT and run for 48 hours until Sunday, May 2nd at 7:00 PM GMT. It will be run on our port 3000 for k=400-600. Tests will likely be in the n=765K to 775K range during the rally.

LLRnet config info.:
server = "www.noprimeleftbehind.net"
port = 3000

Be sure and change your userID to whatever ID you prefer. Most people use their ID here at mersenneforum. It is also best to set the cache at from around 2 to 10 pairs.

This will be the first rally ever run with a full speed LLRnet client running speedy LLR 3.8. Please see information for downloading the new LLRnet client at http://www.mersenneforum.org/showthread.php?t=13165. If anyone prefers, he can still run the old client but it will be slower.

For those of you who would prefer to run PRPnet instead, Max has graciously agreed to set up a private PRPnet server for you with pairs near the same n-range as will be run for the rally. Just let us know at least 3 days ahead of time.

Update: as of 7 PM EDT, 4/30, I (Max) have set up a PRPnet server loaded with n=780K-785K for those interested in using it for this rally. It's running version 3.2.5, so you'll want to use the latest client to ensure ideal performance; see post #24 in this thread for details. The client config info is as follows:
server = "www.noprimeleftbehind.net"
port = 9000
Or, in terms of a prpclient.ini config line:
server=G9000:100:1:noprimeleftbehind.net:9000

As a point of interest for those who might be new to NPLB and for others who haven't done any testing with us for a while, we have some milestones that we would like to shoot for in the near future. Please refer to our primes graph and drive progress at http://www.noprimeleftbehind.net/sta...drive_progress as well as to our "countdown meter" at http://www.mersenneforum.org/showthread.php?t=13333. NPLB's goal all along has been to fill in holes in the prime search ranges for Riesel base 2. We'd like to get the dots in that k=300-1001 range fully extended to n=1M by year end 2011 so that they are closer to where k<300 (worked by RPS) is at. In targeting k=400-600 for this rally, we have set a relatively aggressive goal to have it tested completely to n=1M by year end 2010.

We'll likely be posting this at Free DC and the AMD users group. If others can think of other places that it might be posted, please let us know. I'll also announce it at CRUS.

We'd once again like to make this a more regular thing; perhaps one every 2-3 months.

Personally I think ROLP will kick Free DCs butt this time around. After they had us for a BBQ the last couple of times, we're ready with a surprise or two this time.


Gary

P.S.: Here's a table of all the primes found during this rally:

prime            finder      new/confirmed
545*2^764812-1   gd_barnes   new
405*2^765777-1   jamers      confirmed
407*2^769166-1   gd_barnes   new
489*2^780040-1   Lennart     confirmed
583*2^781515-1   Lennart     new
459*2^782168-1   Lennart     new

[gamer007]

How should I go about to putting a client on each core? Should I just make copies of the folder for the amount of cores or is there an option I can change to let it know how many cores to use?

[kar_bon]

Originally Posted by gamer007

How should I go about to putting a client on each core? Should I just make copies of the folder for the amount of cores or is there an option I can change to let it know how many cores to use?

Make for every core a seperate folder. Copy all files of the LLRnet-client in there and change the 'llr-clientconfig.ini' to the settings given in the first post. That's all.

sample ini-file like:

server = "www.noprimeleftbehind.net"
port = 3000
username = "gamer007"
serviceName = "LLRnet-test1"
WUCacheSize = 1

You can test this antime, so you're sure it works fine when the race starts!

Not mentioned here yet:

The current status (updated every 15 minutes) of the G3000-server is available here.

[gamer007]

Thanks for the help. Will run for a while to see everything runs smoothly.

And to clarify (I went through the LLRnet thread quickly), I have to do "do.bat -c" whenever I quit by ctrl-c right?

[kar_bon]

Originally Posted by gamer007

And to clarify (I went through the LLRnet thread quickly), I have to do "do.bat -c" whenever I quit by ctrl-c right?

No, not every time. The parameter 'jobMaxTime' for all NPLB-servers are set to 2 days, says, the user has 2 days to complete a LLR-test until it's sent again to another client.
So if you will send a result to a server after 3 days, this test will not accepted by the server. If you're sure not to complete a test in 2 days, call 'do -c' and the current test(s) will sent back to the server.

You can start the batch by calling 'do' every time you stopped. The current test will be continued then.

PS: The first 2 results from 'gamer007' are displayed on the status-page!

[gd_barnes]

Karsten,

What does the "serviceName" line do in the llr-clientconfig.txt file? This question was posed by Vaughan in the AMD users thread where we announced the rally.

Is it necessary?


Gary

[mdettweiler]

Originally Posted by gd_barnes

Karsten,

What does the "serviceName" line do in the llr-clientconfig.txt file? This question was posed by Vaughan in the AMD users thread where we announced the rally.

Is it necessary?


Gary

That's so that LLRnet knows what to name itself in Windows' service registry if you set it up to be autostarted as a service upon system boot. If you use that functionality, I think they have to be unique (no two clients on the same machine with the same serviceName). However, that functionality most definitely does not work with the "new" clients (do.bat/pl). I'm not sure if LLRnet still needs it to be specified in order to run, though.

[kar_bon]

Correct, "serviceName" is not needed for running the script with 'do'.

Another reason it was set, when running the GUI of LLRnet, where all clients was shown with results and prime in one window.

[vaughan]

Is it true that we still need to have different folders for each core?
eg
C:\NPLB
C:\NPLB1
C:\NPLB2
C:\NPLB3

and in each we have the llr-clientconfig.txt that contains a different GUIport = line

GUIport = 6999
GUIport = 6998
etc

Also, how do I as simply as possible update from the old LLR to the new 10% faster version?
I tried the thread for the new version and downloaded the file but don't understand how it works. The .bat or .do file or whatever is too arcane for me.

[TimSorbet]

vaughan:
I think it'd be simplest to forget about/delete your old LLRnet setups, download the new package from http://www.mersenneforum.org/showthread.php?t=13165, (which includes the new LLR and do.bat or do.pl, with everything you need) and then set it up:
First, change any options in the beginning of do.bat or do.pl that you wish (see the readme for help). Then make your llr-clientconfig.txt something like this:

server = "www.noprimeleftbehind.net"
port = 3000
username = "vaughan"
WUCacheSize = 3

GUIPort isn't really used/useful any more because LLRnet only runs momentarily to send and receive work. Then make as many copies of the folder as you need, wherever you want them. (note that there is nothing in the files that specifies which instance is which, so you don't have to worry about changing anything between the instances) Then run the do.bat file in each and you're good.
One option for automatic starting of LLRnet on bootup is to put a shortcut to each do.bat in your Startup folder (e.g. C:\Documents and Settings\All Users\Start Menu\Programs\Startup).

[gd_barnes]

Yes, what Tim (Mini-geek) said. Just delete all of your old LLRnet clients and download the new one. That's what I did. The old ones are pointless now.