Testing....

kar_bon · 2010-02-18, 16:46

Backgrounds and purposes

LLRnet is a Client/Server program to calculate primes with LLR.
LLRnet was programmed in 2004-2005 by Vincent Penne in the language LUA. It uses internally the program LLR of Version 3.5 programmed by Jean Penne.

The latest LLR-Version available is 3.8, which is 10%-20% faster than V3.7, with more possibilities in testing different values and less issues in small n-values.

Vincent do not support a newer version of LLRnet, so the idea is to make both (LLRnet and LLR) working together with a script, using the feature for the client/server communication and the speed of the new LLR V3.8!

The LLRnet-client consists of an EXE-file with some other LUA-source files (like Pascal or C), which easily can be edited.

First attempts

The idea was, to skip the primetest in the lua-source by commenting out that line.
So LLRnet will reserve some workunits from the server, saves them in a test-file and quit.
Now LLR take this test-file and do the primetest. After completion the LLR-resultfile have to be converted into the format LLRnet can read. In the next step LLRnet uses the converted resultfile and send it to the server and grabs new workunits again.

That's the (quite easy) theory.

The first small version of the script looked like this:

Code:

 1 :start
 2 if exist z* goto do_cllr
 3 gawk -f do_tosend.awk lresults.txt
 4 type lresults.txt >>lresults_hist.txt
 5 del lresults.txt workfile.res workfile.txt llr.ini
 6 llrnet
 7 del tosend.txt
 8 :do_cllr
 9 cllr -d workfile.txt
10 goto start

2 if there is a cllr-savefile, continue the test
3 convert the cllr-resultfile 'lresults.txt' into 'tosend.txt' for submitting with LLRnet
4 append the current results to a history-file
5 delete all not used files (will be written at every call of do.bat)
6 calling LLRnet to receive new pairs and send old results
7 delete the old LLRnet submit-file
9 calling cLLR and testing all workunits in 'workfile.txt'
10 begin from start

Downloads

The current official Version V0.7 can be downloaded here.
The zip contains all files for the latest LLRnet WIN-version 0.9b7 (client and server) and also the scripts and gawk.exe.

A UNIX version of the script will be done by M.Dettweiler.

The package is pre-configured for a local server (127.0.0.1) and with my user name.
To test start the server (llrserver.exe in server-folder) and then run 'do' (in client-folder).
You can interrupt the script by pressing CTRL-C when cLLR is running (testing a pair).
To restart only call 'do' again or cancel jobs by calling 'do -c'.

ToDo: ReadMe.txt for Win-Version to include.

kar_bon · 2010-02-18, 19:01

ToDo list and suggestions for latter versions

ToDO:

[b]1.[/b] The choice-command in WIN are different in XP and Vista, so the waiting for reconnecting to the server in the script with the command (waiting for 60 seconds):[code]choice /t 60 /d j >nul[/code]
won't work under XP!
Solved on 2010-02-19.

[b]2.[/b] If the workfile.txt contains > 1 workunits and cllr didn't tested all pairs yet, stopping the script and cancelling with "do -c" will cancel [b]all[/b] reserved pairs! -> only not tested pairs to cancel!
Solved in Version 0.7 from 2010-03-06

Suggestions:

1. when cancelling, print the pairs in the lresults.hist.txt with date/time.
-> only counting is printed in lresults-hist.txt, which pairs are displayed only on screen

2. make a sound, if script ended (imagine PC is running offline, no/off monitor -> aware when ends)
-> done with a script option the user can set

3. set the LLR-option OutputIterations by parameter to the script
-> done with a script option the user can set

4. manipulate LLRnet options "WUCacheSize" and "once" by seperate script -> stopping LLRnet
-> not needed: 'once' is not used anymore -> cancelling pairs with script is working

5. submitting LLR-timings to server, rather than time between receive-submit in server-results
-> done in Version 0.8

kar_bon · 2010-02-18, 19:02

Test cases

1. Receiving workunits from server and server crashes.

2. Cancelling workunits with LLRnet -c with the script.

3. Starting script when server dried.

4. Processing a different type of primesearching (normally k*2^n-1 30000000000000:M:1:2:258), so perhaps twins or Sophie-Germain.

5. Process different n-values with many cores (stress-test).

6. Processing small-n/big-k-values with LLR and the conversion script.

kar_bon · 2010-02-18, 19:03

Version history

2010-03-08 V0.8 cancel all jobs at once in llrnet.lua, submitting LLR-timings to server
2010-03-06 V0.7 cancelling works, new script to clean workfile.txt, new option to set by user
2010-02-21 V0.61 waitloop set before loop, comment out 2 lines in llrnet.lua (grabbing new pair although once=1)
2010-02-20 V0.6 cancel-option works, some more changes in llrnet.lua
2010-02-19 V0.51 using sleep.exe (renamed to waits.exe here) from MS Resource Kit
2010-02-17 V0.5 Option -c to cancel jobs (not working properly)
2010-02-14 V0.4 printing date/time in lresults.txt with set, beep when prime found, 5 attempts if no connection to server, primes.txt only created/added when prime found
2010-02-12 V0.3 Printing found primes in extra file, commenting out in llrnet.exe, date/time in lresults.txt
2010-02-11 V0.2 Error handling included, commented LLRnet-outputs, llr.ini with OutputIterations set
2010-02-10 V0.1 First small version worked

kar_bon · 2010-02-18, 22:34

i'm currently working on the cancel-issue. a first test seems (almost) perfect checked by Max: the reserved pairs were all canceled from/at the server.
one thing: yesterday i've changed the reservation-loop in the lua and now the first pair was written twice in the workfile.txt and also cancelled twice! (seems not possible but it was so).

2010-02-20:
first tests with some changes in llrnet.lua the cancel-function seems to work! some more testing needed!

2010-02-21: the version 0.61 now got the fully working code for cancelling reserved pairs.
those were tested by different users without any issue.

kar_bon · 2010-02-19, 14:02

Because CHOICE behave different on my XP and Vista box, i will try another tool.

Possibilities:

1. With PING:
ping 127.0.0.1 -n 60 -w 1000>NUL

waits for 60 seconds.

2. Windows Server 2003 Resource Kit Tools:
sleep.exe

3. Win98 Resource Kit:
sleep.exe

4. UnixTools:
sleep.exe

I think, no.3 is the best choice instead of CHOICE!

Quote:

Originally Posted by mdettweiler

Confirmed, number 3 works on my Windows XP setup as well. If it was designed for Win98, and works on XP and Vista as well, then it should work on pretty much anything.

With Win Vista it's ok, too, so this tool is used in the Win-Version of the script.
I've renamed it to 'waits.exe' (wait seconds), because there're other tools around named 'sleep' which put the PC in sleepmode! But this is not what we want!

gd_barnes · 2010-02-19, 21:29

Karsten,

I need to get a good idea of where we are at in all of this on the Windows client testing. Can you answer the following questions:

1. Please post remaining problems and how they will be resolved.
2. When should I get involved in a Windows test?
3. Can you make all Linux changes except for the script?
4. If no to #3, please post the files/programs changed in Windows.
5. If no to #3, please post the files/programs that are stable right now so that we can begin making changes on the Linux side.

On #2, I'm holding off a little until the files/programs stablize. Once that happens, I can get my new I7 connected and add that to my 2 slow laptop cores for a better test than what I could do before.

#'s 4 & 5 will allow Max or me to start making changes to the Linux client so that we can speed things up a little.

Please don't add any more new features at this point. We want to get this rolled out fairly soon.

Thank you,
Gary

kar_bon · 2010-02-20, 01:04

Quote: