Forum > Linux
SETI MB CUDA for Linux
Tye:
--- Quote from: pp on 27 Jul 2009, 01:21:19 pm ---I can confirm that setiathome-6.08.CUDA_2.2_x86_64-pc-linux-gnu no longer takes 100% CPU (only about 2-4% now on this PC). That's with CUDA 2.2 - I haven't been brave enough to upgrade to CUDA 2.3 yet. Also using nVidia 185.18.14 and BOINC 6.9.0. The only downside so far is that the CPU time column now only shows actual CPU time used which is only a couple of minutes during the 19 minutes CUDA run. So no good way of checking exactly how long a WU takes now unless I monitor the clock manually.
--- End quote ---
Yup, that's been bothering me too. I'm wondering if there's a way to trick it into reporting clock time rather than cpu time... I'm using nvidia 185.18.14 and BOINC 6.6.11 btw since I'd like to do multi-GPU here soon.
riofl:
--- Quote from: Tye on 27 Jul 2009, 02:59:42 pm ---
--- Quote from: pp on 27 Jul 2009, 01:21:19 pm ---I can confirm that setiathome-6.08.CUDA_2.2_x86_64-pc-linux-gnu no longer takes 100% CPU (only about 2-4% now on this PC). That's with CUDA 2.2 - I haven't been brave enough to upgrade to CUDA 2.3 yet. Also using nVidia 185.18.14 and BOINC 6.9.0. The only downside so far is that the CPU time column now only shows actual CPU time used which is only a couple of minutes during the 19 minutes CUDA run. So no good way of checking exactly how long a WU takes now unless I monitor the clock manually.
--- End quote ---
Yup, that's been bothering me too. I'm wondering if there's a way to trick it into reporting clock time rather than cpu time... I'm using nvidia 185.18.14 and BOINC 6.6.11 btw since I'd like to do multi-GPU here soon.
--- End quote ---
6.6.37 was reporting proper cpu/gpu times, but when i went back to 6.6.11 to use multiple devices that time reporting broke. i am not sure if adding a flops statement in app_info.xml will help with that or not.
for the ability to use multiple devices not having proper reporting time is an irritant but one i will gladly put up with until there is a newer version with fixed device code.
koschi:
--- Quote from: sunu on 04 Jul 2009, 03:00:48 pm ---Follow all steps (1-4) below:
1) Use a newer boinc version. The latest is 6.6.36, http://boinc.berkeley.edu/download_all.php . I haven't checked it, I use 6.6.20, direct download link http://boinc.berkeley.edu/dl/boinc_6.6.20_x86_64-pc-linux-gnu.sh
2) Make sure all the appropriate cuda libs from 2.2 toolkit
libcudart.so
libcudart.so.2
libcudart.so.2.2
libcufft.so
libcufft.so.2
libcufft.so.2.2
are in the projects/setiathome.berkeley.edu directory.
3) Edit accordingly your ld.so.conf or the corresponding ld-something file of your distro with the above location of the cuda libs.
4) Place a copy of the cuda client in one of the following locations:
/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin
/sbin
/bin
/usr/games
--- End quote ---
Thanks a lot, especially number 4 I would have never tried, its a little insane ;D
One unit was already successfully validated. The CPU usage on my Q6600 is at roughly 1-2s/1min wall clock time.
The default priority of nice 10 seems to slow the process down on my box, once I switched it to 0 or -5, it processed much faster and collected up CPU time quicker.
riofl:
hmm maybe i should try that. im still using nice 19. im only using 3 of my cpus leaving 1 to handle both gpu apps and my desktop. that seems to be most efficient, running cpus at 100% i found the times dropped from an average of 1 hr 25 min to an hour or under. and thats at nice 19.. maybe i should play a bit in priorities.
riofl:
off topic but i thought if anyone would know it would be here.
is there any utility for x86_64 besides lm_sensors that will properly monitor the GTX285 fans?
I assume this is done with the ADT7473 chip. it is enabled in the kernel but lm_sensors reports back "no driver for Analog Devices ADT7473 yet" and also "unknown adapter NVIDIA i2c adapter".
temps are monitoring just fine i just cannot see the fans.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version