Forum > Linux
SETI MB CUDA for Linux
pp:
Congratulations sunu. My goal is a modest top 2000 like I managed in Seti Classic. I'm slowly reaching there and the upgrade to CUDA 2.3 pushed my RAC on the 9800GT over 5000 now which helps a lot ;D
riofl:
--- Quote from: sunu on 19 Aug 2009, 05:32:30 am ---
--- Quote from: riofl on 18 Aug 2009, 09:11:47 pm ---ahh yes except for one thing. i have seen even this new version of boinc obey the due dates and pick the next workunit from among the newly downloaded. if they stayed in ascending date order i would agree but it does not seem to work that way for me. at least 3 or 4 times so far i noticed a cuda and/or cpu workunit placed on hold to pick up one that had a closer due date that was recently downloaded. this means there is a danger the gpu app will reject a possible vlar before it can be flagged.
--- End quote ---
This happens only for vhar workunits, they have shorter deadlines than the rest. VLARs have "normal" deadlines and they are crunched when their time comes, about x(cache) days after they've been downloaded.
Macros, what pp says. Make sure you're using cuda 2.2 or later together with a compatible nvidia driver.
Shameless plug: I've reached #4 in the top hosts list. I don't know how long I can hold on there though. Attaching pdf for future proof.
--- End quote ---
congrats!!! hehe mine is only a paltry 188 :)
i have had bad luck with 2.3 and had to go back to 2.2 which is flawless for me.
you were right... rac gained 200 points in the last 8 hours. thanks! i didnt think frequent restarting made that huge a difference. still a bit odd with 30min workunits but that seems to be what things are now. not quite sure why. just gonna let it go and see where it falls. maybe in a week or 2 things will level out if its the wu being supplied. or maybe this is the norm for this distribution .. dunno..
after get another gtx285 to replace this tesla and i finish next year's crunching project i think i will get a different motherboard with more x16 slots and wind up with maybe 3 gtx285 in this machine. that should help things along. i think this tesla has seen better days. probably a bad ram chip.
riofl:
--- Quote from: macros on 19 Aug 2009, 04:49:16 am ---
--- Quote from: sunu on 08 Aug 2009, 06:17:55 am ---Back in the days when cuda needed a whole core, I was running a 3+1 config in my quad core. All processes had the lowest priority (19) and I don't think I had any serious slowdown, maybe a minute or so, not more. And this was my everyday desktop so many things were running, firefox with many many tabs, full 3d compiz effects, everyday backups, etc.
Only now that cuda shares a core with the other seti@home tasks, I started renicing them only to make them higher priority than the other seti@home instances. I think -5 is not necessary.
--- End quote ---
Question regarding this. I am using the default settings in app_info.xml's <app_version> for cuda as follows:
--- Code: ---<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</avg_ncpus>
--- End code ---
The problem is, that setiathome-CUDA process has demand obviously higher than that and is able to eat up CPU time of whole one core. That results in other (regular CPU) processes to fight over the CPU time, context switches, cache thrashing etc. ->
--- Code: --- PID PR NI RES SHR %CPU TIME+ COMMAND
15538 39 19 48m 1472 101 13:44.03 AK_V8_linux64_s
15539 39 19 48m 1464 101 20:17.47 AK_V8_linux64_s
15540 39 19 48m 1468 101 20:25.35 AK_V8_linux64_s
15541 39 19 48m 1464 99 19:52.12 AK_V8_linux64_s
15544 39 19 48m 1484 99 20:30.54 AK_V8_linux64_s
15545 30 10 114m 10m 99 18:42.69 setiathome-CUDA
15546 39 19 48m 1488 94 19:55.04 AK_V8_linux64_s
16208 39 19 48m 1488 51 12:22.11 AK_V8_linux64_s
15542 39 19 48m 1472 46 12:14.44 AK_V8_linux64_s
--- End code ---
Now to the question - am I doing something wrong and cuda does not behave correctly?
Or is this normal and I should just set avg_ncpus & max_ncpus to 1, and pin the process to some core + make it use it exclusively?
--- End quote ---
i think you will find best resonse setting your preferences to use 6 or 7 cpus instead of 8 leaving 1 for cuda and your desktop to use. i played around a bit with max_ncpus but did not find a huge difference. mine is set at 0.35.
absolutely if you do nothing else change your cuda tookit and sdk to 2.2 and get the 2.2 application. make sure your driver is at the minimum 185.14 or 185.29. i am using 185.29.
ver 2.1 had huge flaws in it . i have heard 2.3 is even better, however i have not had good luck with 2.3 so i went back to 2.2 until i can figure out what went wrong.
sunu:
Thanks pp, riofl. For a long time I was the only one in the top 100 list using linux. Now I see we are three. I hope more will get in the top 100. We have to show that linux is at least equal to windows for seti crunching.
pp,compared to you I don't think I was that good in seti classic.
Small correction to riofl: The driver versions are 185.18.14 and 185.18.29. Latest is 185.18.31. Macros, if you go to cuda 2.3 you'll need 190.18.
Macros, what card are you using? Maybe that 99% is because your card goes out of memory?
pp:
Thanks sunu. I crunched Classic from the start and had lots of PCs running but I quit when Seti switched to Boinc. I started again with Boinc only a month ago because one of my colleagues challenged me. I keep in front of him with only two GPUs running but I'm planning a Core i7/GTX 295 upgrade to crush him! I never say no to a challenge...;D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version