Forum > Linux
SETI MB CUDA for Linux
lordvader:
I'll try that ...
But I've just switched over to a 2.6.27 kernel, which also has the CPU tasks at 19, and CUDA at 10, and everything seems to be running fine ...
sunu:
--- Quote from: lordvader on 01 Nov 2009, 06:25:02 am ---But I've just switched over to a 2.6.27 kernel, which also has the CPU tasks at 19, and CUDA at 10, and everything seems to be running fine ...
--- End quote ---
Yes, in my ubuntu with 2.6.27-14 I haven't seen such behaviour either. That's why I'm saying that newer kernels might need more aggressive priority settings for cuda.
pp:
Just add this to cron:
--- Code: ---* * * * * renice 0 `pgrep setiathome` >/dev/null
--- End code ---
riofl:
--- Quote from: sunu on 01 Nov 2009, 06:14:20 am ---What priority do your seti apps (CPU and GPU) run?
In sidux (uses 2.6.31-5) I've seen way too slow crunching with the default priorities, 19 for CPU and 10 for GPU tasks. Renicing the GPU tasks to 0, they speeded up considerably. Maybe newer kernels need more aggressive priority levels for cuda.
I'm using the script attached below to renice the cuda tasks to 0 (it runs in infinite loop, checking every 5 seconds for seti cuda tasks, renicing them to 0).
--- End quote ---
can you run gpus at higher levels sucn as -1 or so or is it the nature of the gpu system to not go below 0? just wondering if there is only marginal benefit at running them at -1 or maybe even -5.
i have set that script for cpus as well, so now my gpus run 0 and cpus 10 instead of 19.. so far no noticable probs with the desktop, only time will tell.
lordvader:
I'm currently renicing to 0, and while there's some improvement, it's nowhere near the performance levels of the 2.6.27 kernel.
I'll leave it running overnight so I can get a better gauge of average performance.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version