mersenneforum.org  

Go Back   mersenneforum.org > Prime Search Projects > No Prime Left Behind

Reply
 
Thread Tools
Old 2010-09-29, 22:21   #155
gd_barnes
 
gd_barnes's Avatar
 
May 2007
Kansas; USA

23×33×47 Posts
Default

Quote:
Originally Posted by mdettweiler View Post
Ah, good catch. I changed it in the script's internal comments but not in the readme. That is fixed now and the corrected zip file is uploading right now. (I also added an entry in the changelog indicating that the version number was changed to match the Windows script, but that no actual changes to the do.pl script were made.)

Karsten, just to clarify: are you using V0.73 or V0.74 to denote the latest version of your script with LLR 3.8.2 in it? Either's fine with me, but if you're sticking with V0.73 then I should probably make sure that the Linux client matches that instead of being V0.74 (since, after all, the whole point of raising the version number is so that they match).
You do realize that you did not respond to my first point in the first para here. Correct?

Last fiddled with by gd_barnes on 2010-09-29 at 22:36
gd_barnes is online now   Reply With Quote
Old 2010-09-29, 22:37   #156
gd_barnes
 
gd_barnes's Avatar
 
May 2007
Kansas; USA

23·33·47 Posts
Default

Max,

The Linux client does not work with LLR 3.8.2. It keeps exiting immediately. Please test and correct it when you get a chance. Thanks.

Edit: A second attempt says that pairs are not available. The first attempt, I just plopped the LLR binary in my existing folder since there was no coding change to the script; only the comments changed. The second attempt, I used all of your files, just in case something else changed that I wasn't aware of. Both ways, no luck. I made sure I had the llrnetcongif configured correctly.


Gary

Last fiddled with by gd_barnes on 2010-09-29 at 22:54
gd_barnes is online now   Reply With Quote
Old 2010-09-29, 22:55   #157
gd_barnes
 
gd_barnes's Avatar
 
May 2007
Kansas; USA

23·33·47 Posts
Default

BTW, are you guys aware that the LLR 3.8.2 binary jumped to ~25 MB from LLR 3.8.1 that was only ~5 MB? Is this really something where we can just plop the binary into our existing folders on LLRnet and/or PRPnet? After my problems, I think we need to fully test the new clients.

Last fiddled with by gd_barnes on 2010-09-29 at 22:58
gd_barnes is online now   Reply With Quote
Old 2010-09-29, 23:01   #158
rogue
 
rogue's Avatar
 
"Mark"
Apr 2003
Between here and the

580010 Posts
Default

Quote:
Originally Posted by gd_barnes View Post
BTW, are you guys aware that the LLR 3.8.2 binary jumped to ~25 MB from LLR 3.8.1 that was only ~5 MB? Is this really something where we can just plop the binary into our existing folders on LLRnet and/or PRPnet? After my problems, I think we need to fully test the new clients.
Yes, it is larger. George added a lot of code to support additional FFT sizes.
rogue is offline   Reply With Quote
Old 2010-09-29, 23:43   #159
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

3·2,083 Posts
Default

Quote:
Originally Posted by gd_barnes View Post
You do realize that you did not respond to my first point in the first para here. Correct?
Ah, whoops. I was thinking that at this point, we may as well keep it at 0.74. But I can change it back if you'd like. Either way's fine with me.
Quote:
Originally Posted by gd_barnes View Post
Max,

The Linux client does not work with LLR 3.8.2. It keeps exiting immediately. Please test and correct it when you get a chance. Thanks.

Edit: A second attempt says that pairs are not available. The first attempt, I just plopped the LLR binary in my existing folder since there was no coding change to the script; only the comments changed. The second attempt, I used all of your files, just in case something else changed that I wasn't aware of. Both ways, no luck. I made sure I had the llrnetcongif configured correctly.


Gary
Hmm, very strange. The new LLR should handle input and output files exactly the same--all that was changed was the gwnum version, which just changes some of the screen output regarding FFT sizes. It should not affect anything the do.pl script cares about.

I'll try testing it, though, and see what happens for myself. Clearly there is some difference in how LLR 3.8.2 handles its input and ouput files and it's making the do.pl script go nuts.

Regarding the size of the llr binary: as Mark said, that's due to a lot more CPU-specialized code being packed into the latest gwnum. This is why LLR 3.8.2 is usually faster than 3.8.1.
mdettweiler is offline   Reply With Quote
Old 2010-09-30, 00:03   #160
gd_barnes
 
gd_barnes's Avatar
 
May 2007
Kansas; USA

236508 Posts
Default

Ah, heck yeah on the speed increase! Wee! When using PFGW 3.4.0 (Linux) and 3.4.1 (Windows), BIG speed up my CRUS base 28 stuff. 20% or more! I think Karsten is getting that increase or better on his n>1M base 2 stuff here. Very nice!

Yeah, I suspect there is some sort of input-output difference to/from the new LLR. It's always good to run a quick test before posting new software even if the change is what should be a small one.

Last fiddled with by gd_barnes on 2010-09-30 at 00:04
gd_barnes is online now   Reply With Quote
Old 2010-09-30, 02:59   #161
kar_bon
 
kar_bon's Avatar
 
Mar 2006
Germany

23×353 Posts
Default

Quote:
Originally Posted by gd_barnes View Post
Yeah, I suspect there is some sort of input-output difference to/from the new LLR. It's always good to run a quick test before posting new software even if the change is what should be a small one.
As I mentioned, I've checked this and done as described for the WIN-script:
- stop client
- overwrite cLLR.exe with new one (Hint: use cLLR.exe not LLR.exe, the command version, not GUI-version!)
- start again client

I've done this with all of my 16 cores (XP, Vista, WIN7) and no problems occured.
Possible problem: Converting from lresults.txt to tosend.txt (check/test do.pl)

Please check again with UNIX.

The comments/screen outputs changed, because I've not patched again cLLR.exe, for example:
Code:
[2010-09-30 04:26:50]
  Fetching WU #1/1: 327 1158098
Starting Lucas Lehmer Riesel prime test of 327*2^1158098-1
Using Core2 type-1 FFT length 72K, Pass1=96, Pass2=768
V1 = 3 ; Computing U0...done.
327*2^1158098-1 is not prime.  LLR Res64: A4385FD1358EAB68  Time : 1607.416 sec.
[2010-09-30 04:53:40]

But this has no effect on the lresults.txt file.
I've not yet updated the download-zip with the new cLLR version, because waiting for the next version would be better.

Last fiddled with by kar_bon on 2010-09-30 at 03:06
kar_bon is offline   Reply With Quote
Old 2010-09-30, 05:18   #162
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

624910 Posts
Default

Okay, I found the problem. Turns out the llrnet and llr binaries didn't have +x permissions on them when they came out of the zip file. (Duh.) Running chmod +x on them got it working, so I replaced the binaries in the zip file with the +x'ed ones and re-uploaded it to the web site.

Gary, let me know if this one works. (It should work, since I really did test it this time. On a real Linux machine, too--one of yours, in fact. )

Edit: oh, and now that I've figured out what went wrong I can confirm that it should be OK to swap in the new LLR binary directly to an old do.pl client. If it doesn't work, run "chmod +x llr" and try again.

Last fiddled with by mdettweiler on 2010-09-30 at 05:22
mdettweiler is offline   Reply With Quote
Old 2010-09-30, 11:11   #163
gd_barnes
 
gd_barnes's Avatar
 
May 2007
Kansas; USA

23·33·47 Posts
Default

Quote:
Originally Posted by kar_bon View Post
Jean Penné just released the new LLR V3.8.2 with gwnum-lib 26.2.

He mentioned a 10% faster testing with that version.

To use the new cLLR, download it from here, stop the client-script by hitting CTRL-C, overwrite the old cLLR.exe with the downloaded one and start the script again by calling 'do'.

I'll check if the speed is as assumed.

Later on I'll update the links in the first post with this new cLLR version.
The link does not work. I went directly to his page and there is no Windows or Linux 3.8.2 version. For my Linux machines, I used what Max posted in the 1st post here. I can't update my Windows machine now. Is 3.8.2 somewhere else?
gd_barnes is online now   Reply With Quote
Old 2010-09-30, 11:41   #164
kar_bon
 
kar_bon's Avatar
 
Mar 2006
Germany

23·353 Posts
Default

Quote:
Originally Posted by gd_barnes View Post
I can't update my Windows machine now. Is 3.8.2 somewhere else?
All links work fine for me here.

I've uploaded the cLLR V3.8.2 WIN here, too.
kar_bon is offline   Reply With Quote
Old 2010-09-30, 14:29   #165
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

3×2,083 Posts
Default

Quote:
Originally Posted by gd_barnes View Post
The link does not work. I went directly to his page and there is no Windows or Linux 3.8.2 version. For my Linux machines, I used what Max posted in the 1st post here. I can't update my Windows machine now. Is 3.8.2 somewhere else?
In addition to the link Karsten posted, you can download all the LLR 3.8.2 versions at:
http://jpenne.free.fr/Development/
It's not on Jean's main page since it's still a "development" version at this point. (So it's a kind of beta version, but should still be stable enough for use on production work.)
mdettweiler is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
LLRNET ValerieVonck Software 12 2010-03-15 18:09
llrnet 64 bit balachmar Prime Sierpinski Project 4 2008-07-19 08:21
LLRNet em99010pepe Riesel Prime Search 20 2007-09-11 21:03
Bush Supports $120 Billion Iraq War Compromise ewmayer Soap Box 23 2007-05-27 12:37
LLRnet over proxy? Bananeweizen Sierpinski/Riesel Base 5 4 2006-10-14 07:51

All times are UTC. The time now is 04:10.

Fri Jul 10 04:10:27 UTC 2020 up 107 days, 1:43, 0 users, load averages: 2.58, 2.28, 1.84

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.