Forum > Linux
SETI MB CUDA for Linux
sunu:
Yes I still have a Q6600, it's my other "big" machine http://setiathome.berkeley.edu/show_host_detail.php?hostid=3281360 . This has the old ubuntu kernel that saw the slowdown with negative nice levels. This has an ASUS P5K vanilla motherboard. With this machine I didn't see much difference going from 10-19 GPU-CPU to 0-19 GPU-CPU.
--- Quote from: riofl on 02 Nov 2009, 09:22:17 am ---i did notice an apparent slow down using -5 so i went back to 0 but again that was short term.
--- End quote ---
So we see the same result, at least with my ubuntu machine using the old, 2.6.27-14 kernel.
The 3690316 is a new lightweight experimental/testing build I've made to use it for... well experimental/testing things. Right now it runs sidux and boinc with all cuda and stuff over livecd.
riofl:
ahh ok so the difference was not that great with the 'big' machine compared to the others... now i dont feel so bad :)
my workstation is using 2.6.29 kernel and i doubt i will update it knowing what i do now.. i have the script running to set cpu nice to 10 to see if it helps on those servers that must run 2.6.31. i did notice rac dropped on those machines so i hope this helps. the rest are 2.6.26 and will be left alone unless my test on one of those proves nice 10 is considerably faster with little bother to the server.
lordvader:
Well I had the units run overnight with the renice script running in the background, and it really made no difference.
CUDA workunits under the 2.6.31 kernel take between 2-4 times longer than they should. I may add, that while these units are running, compositing effects (such as wobbly windows and other eye candy) are extremely stuttery. This wasn't the case with the 2.6.27 kernel.
I'm running a phenom 955 CPU, GTX 275 GPU.
sunu:
Now your machine says 2.6.31-14-generic kernel. Couple of days ago I think I saw it showing 2.6.31-14-custom or something like that.
Looking at your tasks I see most of them with good times and some others with abnormal times all seemingly mixed up.
We are now nearing midnight UTC. Please stick with one kernel, run the script and let it crunch so all workunits reported 3 Nov are with the new 2.6.31 kernel with script running so we can see what's going on.
riofl:
after running gpu at 0 all day with the 2.6.29 kernel it appears my average is down by a few hundred points, so i am cancelling the script for the next 24 hrs to see if it goes back up
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version