Results 1 to 40 of 187

Thread: Automated primality testing with LLRnet for CRUS

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518

    Automated primality testing with LLRnet for CRUS

    I need more testers....the servers have small candidates to test. On a P4 3.0 GHz kn pair is tested in less than 500 seconds from Sierpinski side and less than 300 seconds on Riesel side.

    Quote Originally Posted by Anonymous
    Hi all,

    We now have an official Conjectures 'R Us LLRnet server! (Actually we have two of them. More on that later...)

    With LLRnet, you can perform primality tests (LLR/Proth/PRP) automatically. No need to mess with reserving/reporting ranges and all that stuff. No need to worry about whether your machine will run out of work in the middle of the night or while you're on vacation. Just set it and forget it!

    LLRnet is very simple to set up--in less than 5 minutes you can be all set and crunching away! It's perfect for users who just want to donate their spare CPU cycles to a worthy cause without adding a degree of complexity to their computer use. (That's not to say that it isn't great for advanced users, too. ) It's also great for work computers, since you can set it up on a computer and not have to worry about having it run out of work while it's not accessible. (We've set up one of our LLRnet servers on port 443 for just this reason. If this whole "port" thing is just going in one ear and out the other, though, here's essentially what it means: you're still able to use LLRnet at work even if your company has a restrictive firewall. Sorry, there's currently no way to run LLRnet through an HTTP or SOCKS proxy server, however.)

    Here's all you need to do:

    1. Download the LLRnet client software for your operating system. LLRnet is available for Windows, Linux, and FreeBSD, in two versions: the "stock" version that only works with work for bases that are powers of 2 (but has a nice GUI), and the SR5 version, which works for all bases (but doesn't have the GUI). If you'd rather not have to worry about using different LLRnet installs for different bases, get the SR5 version. If the GUI is a must-have, though, you'll want to use the stock version for bases that are powers of 2.

    Click one of the following links to download LLRnet:

    Windows (SR5 version) <<--------- Recommended for most users
    Linux (SR5 version)<<------------ Recommended for most users

    Windows (stock version, power-of-2 bases only)
    Linux (stock version, power-of-2 bases only)
    FreeBSD (stock version, power-of-2 bases only)

    2. Extract the files from the archive you just downloaded. C:\llrnet is a good choice (or /home/username/llrnet for Linux users).

    3. Navigate to the folder where you extracted LLRnet. Open up the llr-clientconfig.txt file in your favorite text editor. You'll notice a little ways down from the top a line that says the following:

    port = 443

    This is the port on the LLRnet server that the client will connect to. Currently, the LLRnet server is set up to answer on two different ports, each with a different type of numbers. Here's what they currently are:

    443 - Sierpinski Base 16 (Team Drive #1) (default)
    444 - Riesel Base 16 (Team Drive #2)


    Simply change the port value to work on different numbers. Please note that if you're behind a corporate firewall, you might only be able to use port 443. (Corporate firewalls usually allow access on port 443.)

    A little farther down you'll notice another line that says the following:

    username = "nobody"

    Change "nobody" to your mersenneforum.org username. For example, I would set this to "Anonymous". This ensures that numbers you work on are credited properly to you in the stats that will be published periodically. (If you'd rather crunch anonymously, i.e. not have your crunching associated with your mersenneforum.org username, simply set this to something different. You can actually punch in anything you want here, though most users will probably want to punch in your mersenneforum username.)

    Save the file, and close out your text editor.

    4. Doubleclick on the file named "llrnet.exe" to start LLRnet and get crunching! (On Linux and FreeBSD this will be just "llrnet".) You'll see an LLRnet icon appear in your system tray if you're running Windows, and, if you're using the "stock" version of LLRnet, you can right-click on the icon and click a button to pop up a GUI from which you can monitor your work. If you're using the SR5 version (the recommended version since it works for all bases), you can click another button on the right-click menu to open up a console and monitor your work from there. (Note: When you want to close out the console window, don't just close out the window. Instead, right-click on the LLRnet icon, and click "detach console". Otherwise, you'll close out the LLRnet program, which you probably don't want to do.) You can also use the console with the stock version, just like with the SR5 version. Linux users won't see a system tray icon, but they will get a GUI that pops up if they're using the stock version. (If you want to get the GUI back up after closing it out, navigate to your LLRnet folder and run the remote-gui.sh file.) To see the console, you'll want to start LLRnet from a command window--navigate to the LLRnet folder, and type the command "./llrnet" (without quotes). (With the console open, simply press Ctrl-C to stop LLRnet.)

    5. If you want to have LLRnet run automatically when you start your computer, simply right-click the LLRnet system tray icon and click "Add LLRnet service". Or, if you'd rather only run LLRnet when your username is logged on, click the Start button, and navigate to All Programs, then double-click on the item named "Startup". A folder window will open. In a separate window, navigate to your LLRnet folder. Drag the llrnet.exe icon, with the right mouse button, to the Startup folder, and let go of the mouse button. Choose "Create Shortcut" from the menu that appears.

    For Linux, how you set a program to run at startup depends on your distribution. Just post a message here and someone will try to help.

    That's all!

    Please post any questions/comments here, or send a private message to me (Anonymous).

    Special thanks to Carlos (em99010pepe) for graciously hosting the LLRnet server for us!

    Let's get crunching!
    Quote Originally Posted by Anonymous
    Q: Can I run LLRnet on a multi-core system and still utilize all the cores?
    Yes, though LLRnet by default can only utilize one core. Thus, you'll have to run multiple copies of LLRnet. Simply, when installing, extract the archive you downloaded into as many folders as you have cores (such as c:\llrnet, c:\llrnet2, etc.). Then, configure the llr-clientconfig.txt for each core (you have to configure each installation separately--and if you're using the stock version, make sure to change the GUIPort value to something different on everything except the first installation. You'll also have to change this value in the llr-guiconfig.txt for the installations that have been set to a different GUIPort.), and run the llrnet.exe (or "llrnet" on Linux/FreeBSD) in each installation. You'll see as many LLRnet icons in your system tray as you have cores--you can control each core's LLRnet separately. (You can also configure one core's GUI, if you're using the stock LLRnet, to control all the other cores, too, though that's a little bit more of an advanced topic--you can either try to figure it out on your own, or just post here begging for help. )
    Last edited by em99010pepe; 01-25-2008 at 04:56 PM.

  2. #2
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    NPLB (No Prime Lef Behind Project) server is up and running on crus.dynip.telepac.pt port 300.

    NPLB is searching for all 400 < k <= 1001 for n=260K-320K and n=320K-333.2K at the same time. LLRNet with 321.6K-322.6K range, less than two minutes per candidate. We really need to clean these small ranges. PLEASE HELP.

  3. #3
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    BTW, for future stats please use your username as:

    username = "TeamName_yournickname"

    My case:

    username="Free-DC_em99010pepe"

  4. #4
    Target Butt IronBits's Avatar
    Join Date
    Dec 2001
    Location
    Morrisville, NC
    Posts
    8,619
    Ok, I'll lend a hand for a bit.

  5. #5
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    Quote Originally Posted by IronBits View Post
    Ok, I'll lend a hand for a bit.
    Please use port 300 and not 443, faster wu's. Thanks.

  6. #6
    Target Butt IronBits's Avatar
    Join Date
    Dec 2001
    Location
    Morrisville, NC
    Posts
    8,619
    ok,
    The server refused your new result :
    either someone else computed it already,
    either the server is now configured to
    work on other numbers.
    The server refused your new result :
    either someone else computed it already,
    either the server is now configured to
    work on other numbers.

  7. #7
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    833*2^322530-1 is prime! (IronBits, LLRNet)

  8. #8
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    A 24 hour rally will be held this Friday or Saturday for k/n pairs of port 300. Soon I'll post more details...we really need to clean the lower ranges.

  9. #9
    Target Butt IronBits's Avatar
    Join Date
    Dec 2001
    Location
    Morrisville, NC
    Posts
    8,619
    I'll be there with two Q6600s, one 32bit, the other 64bit.
    Hot diggity dog, found me another Prime

  10. #10
    Ancient Programmer Paratima's Avatar
    Join Date
    Dec 2001
    Location
    West Central Florida
    Posts
    3,296
    Ah'm in with one 3GHz AMD core.
    HOME: A physical construct for keeping rain off your computers.

  11. #11
    Ancient Programmer Paratima's Avatar
    Join Date
    Dec 2001
    Location
    West Central Florida
    Posts
    3,296
    Using Port 300.

    Seems to be averaging about 165 seconds to find a non-prime.
    HOME: A physical construct for keeping rain off your computers.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •