Collatz 4.xx Applications Released for Linux
log in

Advanced search

Message boards : News : Collatz 4.xx Applications Released for Linux

Author Message
Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 16136 - Posted: 28 Mar 2013, 16:34:41 UTC

32 and 64 bit Linux applications have been released for CPU, CUDA, and OpenCL ATI. The CUDA and OpenCL applications are limited to mini_collatz and should be considered experimental at this time as they are not fully tested.

Profile 7ri9991 [MM]
Avatar
Send message
Joined: 24 Aug 09
Posts: 13
Credit: 146,823,460
RAC: 0
Message 16138 - Posted: 28 Mar 2013, 16:49:11 UTC - in response to Message 16136.

Is this the same app shipped with the app_info version or a new one that is possibly faster?

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 16140 - Posted: 28 Mar 2013, 17:23:50 UTC - in response to Message 16138.

Is this the same app shipped with the app_info version or a new one that is possibly faster?


These are NEW. They all use the collatz.config which elminiates the need for an app_info.xml. The will also work with an app_config.xml to run multiple versions at one time which may be easier than trying to tweak the collatz.config settings to get a single WU to run at optimal speed.

Eventually, the 2.xx and 3.xx will be deprecated as this new app does not require a wingman. At present, it is set to run with a wingman, but as soon as apps are deployed for all platforms and have proven to match results, the work generator and validator will be updated to no longer require a quorum of 2.

Profile 7ri9991 [MM]
Avatar
Send message
Joined: 24 Aug 09
Posts: 13
Credit: 146,823,460
RAC: 0
Message 16147 - Posted: 30 Mar 2013, 0:33:53 UTC - in response to Message 16140.
Last modified: 30 Mar 2013, 0:57:59 UTC

Something isn't quite right. Tasks are taking 7 times longer and apparently using a full core. Odd since I have CPU deselected. So far I've completed 3, but no wingman joy, yet.

EDIT: Gentoo stable is at Cuda 4, but I'm currently installing Cuda 5 to see if it helps. It's taking all day to download, though.

Profile kmanley57
Send message
Joined: 1 Apr 12
Posts: 6
Credit: 32,623,691
RAC: 0
Message 16149 - Posted: 30 Mar 2013, 13:28:20 UTC

They are taking a long time to run! 6+ hours for a mini-collatz. I look forward to seeing the results of the change over. I hope there is a change I can do to get them to run faster for sure!!!

Profile 7ri9991 [MM]
Avatar
Send message
Joined: 24 Aug 09
Posts: 13
Credit: 146,823,460
RAC: 0
Message 16151 - Posted: 30 Mar 2013, 15:09:30 UTC

Installed cuda-toolkit-5, no change. Still takes 6 times as long and I doubt it even uses the GPU. (no proof on that statement)

Gary Wilson
Send message
Joined: 1 Jan 10
Posts: 2
Credit: 40,026,222
RAC: 0
Message 16152 - Posted: 30 Mar 2013, 15:13:34 UTC
Last modified: 30 Mar 2013, 15:14:59 UTC

Seeing the same thing. Thermals on the GPU act as if it's idle, meaning, temps are about the same when it's idle. Full core of CPU is used as well. This is on an 8800GT/Ubuntu 12.04.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 16186 - Posted: 5 Apr 2013, 14:06:33 UTC - in response to Message 16151.

Installed cuda-toolkit-5, no change. Still takes 6 times as long and I doubt it even uses the GPU. (no proof on that statement)


It might have been, but have no way to prove it as I don't have a Linux box with a CUDA GPU. I made some changes to the app and redeployed it as v4.04. I'd appreciate it if someone could give it a try and let me know whether it is working now or not.

Profile 7ri9991 [MM]
Avatar
Send message
Joined: 24 Aug 09
Posts: 13
Credit: 146,823,460
RAC: 0
Message 16191 - Posted: 5 Apr 2013, 23:41:19 UTC - in response to Message 16186.
Last modified: 6 Apr 2013, 0:01:14 UTC

It might have been, but have no way to prove it as I don't have a Linux box with a CUDA GPU. I made some changes to the app and redeployed it as v4.04. I'd appreciate it if someone could give it a try and let me know whether it is working now or not.


Just tried it. Nothing but compute errors.

http://boinc.thesonntags.com/collatz/result.php?resultid=137682120

Kind of surprised this isn't a static app. Here's what my Gentoo box is linking to.
ldd mini_collatz_4.04_x86_64-pc-linux-gnu__cuda50
linux-vdso.so.1 (0x00007fff806e6000)
libcudart.so.5.0 => /opt/cuda/lib64/libcudart.so.5.0 (0x00007fd8e07e8000)
libm.so.6 => /lib64/libm.so.6 (0x00007fd8e04f2000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1 (0x00007fd8e02dc000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd8e00bf000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd8dfd15000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd8e0a42000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fd8dfb11000)
librt.so.1 => /lib64/librt.so.1 (0x00007fd8df908000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6 (0x00007fd8df604000)


EDIT: Another thing I notice and not sure if it matters, but if the app is looking for "libcudart.so.5.0", shouldn't it ship with the app? What ships is libcudart.so.5.0.35_x86_64.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 16193 - Posted: 6 Apr 2013, 2:29:47 UTC - in response to Message 16191.

It might have been, but have no way to prove it as I don't have a Linux box with a CUDA GPU. I made some changes to the app and redeployed it as v4.04. I'd appreciate it if someone could give it a try and let me know whether it is working now or not.


Just tried it. Nothing but compute errors.

http://boinc.thesonntags.com/collatz/result.php?resultid=137682120

Kind of surprised this isn't a static app. Here's what my Gentoo box is linking to.
ldd mini_collatz_4.04_x86_64-pc-linux-gnu__cuda50
linux-vdso.so.1 (0x00007fff806e6000)
libcudart.so.5.0 => /opt/cuda/lib64/libcudart.so.5.0 (0x00007fd8e07e8000)
libm.so.6 => /lib64/libm.so.6 (0x00007fd8e04f2000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1 (0x00007fd8e02dc000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd8e00bf000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd8dfd15000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd8e0a42000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fd8dfb11000)
librt.so.1 => /lib64/librt.so.1 (0x00007fd8df908000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6 (0x00007fd8df604000)


EDIT: Another thing I notice and not sure if it matters, but if the app is looking for "libcudart.so.5.0", shouldn't it ship with the app? What ships is libcudart.so.5.0.35_x86_64.


Technically, libcudart.so.5.0 is a symbolic link to libcudart.so.5.0.35 and while BOINC doesn't do symbolic links, it should be renaming it. That's why the file is named "libcudart.so.5.0=libcudart.so.5.0.35_x86_64" and there is an additional file named "libcudart.so.5.0=libcudart.so.5.0.35_x86_64.file_ref_info" with the contents "<copy_file/>" (anotherer BOINCism) so that the file gets copied into the project folder.
The app is compiled with "-static-libgcc" and against libstdc++.a in the same folder as the source which is a symbolic link to the real file. In other words, it uses the BOINC CUDA sample Makefile with the only difference being the name of the source files. While I know enough about Linux to make it work on my system, I don't know enough about how to make it work on ALL systems and we all know that a little knowledge can be dangerous. So, if anyone has any suggestions, I'd love to hear them.

I do find it interesting that ldd on the CPU app does NOT show it linked to the shared libraries. Is CUDA linked to the shared libraries? Or, do I need to use symbolic links to the CUDA libraries the same way as the C++ library is symbolically linked?

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 16194 - Posted: 6 Apr 2013, 3:35:48 UTC - in response to Message 16191.

It might have been, but have no way to prove it as I don't have a Linux box with a CUDA GPU. I made some changes to the app and redeployed it as v4.04. I'd appreciate it if someone could give it a try and let me know whether it is working now or not.


Just tried it. Nothing but compute errors.

http://boinc.thesonntags.com/collatz/result.php?resultid=137682120

Kind of surprised this isn't a static app. Here's what my Gentoo box is linking to.
ldd mini_collatz_4.04_x86_64-pc-linux-gnu__cuda50
linux-vdso.so.1 (0x00007fff806e6000)
libcudart.so.5.0 => /opt/cuda/lib64/libcudart.so.5.0 (0x00007fd8e07e8000)
libm.so.6 => /lib64/libm.so.6 (0x00007fd8e04f2000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1 (0x00007fd8e02dc000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd8e00bf000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd8dfd15000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd8e0a42000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fd8dfb11000)
librt.so.1 => /lib64/librt.so.1 (0x00007fd8df908000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6 (0x00007fd8df604000)


EDIT: Another thing I notice and not sure if it matters, but if the app is looking for "libcudart.so.5.0", shouldn't it ship with the app? What ships is libcudart.so.5.0.35_x86_64.


It should look different if you do the ldd from the slot folder. Or is that where it was done from?

Profile 7ri9991 [MM]
Avatar
Send message
Joined: 24 Aug 09
Posts: 13
Credit: 146,823,460
RAC: 0
Message 16196 - Posted: 6 Apr 2013, 15:01:09 UTC - in response to Message 16194.

It might have been, but have no way to prove it as I don't have a Linux box with a CUDA GPU. I made some changes to the app and redeployed it as v4.04. I'd appreciate it if someone could give it a try and let me know whether it is working now or not.


Just tried it. Nothing but compute errors.

http://boinc.thesonntags.com/collatz/result.php?resultid=137682120

Kind of surprised this isn't a static app. Here's what my Gentoo box is linking to.
ldd mini_collatz_4.04_x86_64-pc-linux-gnu__cuda50
linux-vdso.so.1 (0x00007fff806e6000)
libcudart.so.5.0 => /opt/cuda/lib64/libcudart.so.5.0 (0x00007fd8e07e8000)
libm.so.6 => /lib64/libm.so.6 (0x00007fd8e04f2000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1 (0x00007fd8e02dc000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd8e00bf000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd8dfd15000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd8e0a42000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fd8dfb11000)
librt.so.1 => /lib64/librt.so.1 (0x00007fd8df908000)
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libstdc++.so.6 (0x00007fd8df604000)


EDIT: Another thing I notice and not sure if it matters, but if the app is looking for "libcudart.so.5.0", shouldn't it ship with the app? What ships is libcudart.so.5.0.35_x86_64.


It should look different if you do the ldd from the slot folder. Or is that where it was done from?


It errors out too fast to try. Maybe I could copy it to a faux slot folder before it dies and try it from there.

I realize libcudart.so.5.0 is a symbolic link. That's why I was confused that the app was looking for a symbolic link that didn't dome with it. I was able to copy a slot folder over before the task died and here are the files that got copied over.

boinc_lockfile
boinc_mmap_file
collatz.config
in.txt
init_data.xml
libcudart.so.5.0
mini_collatz_4.04_x86_64-pc-linux-gnu__cuda50
out.txt
stderr.txt


I did notice that the libcudart file was the right name and the same size as libcudart.so.5.0.35_x86_64. The one on my system has a different size.

I tried to run the app local, not knowing if there was some commandline or not for starting it. I copied the task to in.txt and created an empty out.txt. I also copied over the collatz.config file. Running the app without any inputs gave me this.

./mini_collatz_4.04_x86_64-pc-linux-gnu__cuda50
Floating point exception


...and the contents of the stderr.txt file.

09:43:05 (3310): Can't open init data file - running in standalone mode
Collatz Conjecture v4.04 x86_64 for CUDA 5.0
Based on the AMD Brook+ kernels by Gipsel
verbose=1
Name GeForce GTX 460
Compute 2.1
Parameters
Start 2378995064202056149352
Checking 103079215104 numbers
Numbers/Kernel 65536
Kernels/Reduction 256
Numbers/Reduction 16777216
Reductions/WU 6144
Threads 0
Reduction CPU


Don't know if that helps at all.


Post to thread

Message boards : News : Collatz 4.xx Applications Released for Linux


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.