Seti@Home optimized science apps and information
Optimized Seti@Home apps => Linux => Topic started by: s52d on 15 Aug 2009, 08:11:16 am
-
While my slackware 64 works fine, I would like to upgrade to faster libraries.
It took me awhile to get it working, so I am a bit scared (and not much time to experiment).
Would it be enoug to:
grab toolkit and copy only lib64 libraries to /usr/lib64
- and copy them to boinc directories over old libraries as well?
then do new cudadriver on top of it?
BR, 73
Iztok
libraries in lib64 directory of cudatoolkit_2.3_linux_64_rhel5.3.run
-rwxr-xr-x 1 iztok users 1508896 2009-08-15 11:32 libcufftemu.so.2.3*
-rwxr-xr-x 1 iztok users 8714504 2009-08-15 11:32 libcufft.so.2.3*
-rwxr-xr-x 1 iztok users 260840 2009-08-15 11:32 libcudart.so.2.3*
-rwxr-xr-x 1 iztok users 5067736 2009-08-15 11:32 libcublasemu.so.2.3*
-rwxr-xr-x 1 iztok users 15608280 2009-08-15 11:32 libcublas.so.2.3*
driver file: cudadriver_2.3_linux_64_190.18.run
-
Yes, you'll need a cuda 2.3 capable driver to go along with the 2.3 libs. 190.18 is ok.
For proper cuda installation for seti@home see my post here (http://lunatics.kwsn.net/linux/seti-mb-cuda-for-linux.msg19014.html#msg19014) and follow it carefully.
If you use multiple gpus you'll have to use 6.6.11 or try compiling boinc from source.
-
OK, I did it.
1. new libraries to /usr/lib64 and /home/boinc/boinc also /home/boinc/boinc/projects/setiathome.berkeley.edu
2. ldconfig (and fix few sibolic links)
3. stop X (should be done as step 0, of course)
4. install new nvidia driver
5. startx
6. start boinc
Works - let me see, if it validates. But mostly, if it works then it validates.
cuda task is taking some 10% of one CPU with GTX 260 and Q6600.
Thanks,
Iztok
partially old/partial new: validated.
fist fully new libraries, http://setiweb.ssl.berkeley.edu/result.php?resultid=1317693933
96 seconds for 120 claimed credits, wow!
-
You could also try a bit newer cuda app from this (http://calbe.dw70.de/mb/viewtopic.php?f=9&t=110) thread (about mid point, setiathome-CUDA_2.2_6.08.x86_64_vlarkill).
If you do this, change accordingly your app_info.xml as the new client has a different name and also DON'T FORGET STEP 4 FROM MY POST I LINKED ABOVE.