Forum > Linux
SETI MB CUDA for Linux
riofl:
--- 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 ---
i tried setting the AK MB cpu apps to 10 and the cuda ones to -5 and after 24 hrs there was very little difference in my scores. the only thing that happened is my desktops became difficult to work with and gave me the impression i was working with my old p3 933mhz machine so i returned them to boinc defaults of 19 and 10.
sunu:
A small update for those with multi-gpu systems.
The problem with proper multi-gpu support in linux with recent boinc releases seems to have been fixed (got a message yesterday from David Anderson and I confirmed it compiling boinc and running it).
But now there seems to be another problem with task scheduling. Richard Haselgrove hinted that maybe this problem is general since there have been similar reports that this might also occur in windows. If it is so we might get a faster fix this time.
Well, anyway, we are one problem down. I hope we get a proper functioning boinc in linux soon.
Kunin:
Great news! Maybe soon I won't have to use 6.4.5 for crunching and 6.6.11 for downloading (for some reason 6.6.11 would randomly stop using the GPUs, but 6.4.5 always says high priority so would never download new WU).
sunu:
--- Quote from: Kunin on 14 Aug 2009, 07:06:30 am ---Great news! Maybe soon I won't have to use 6.4.5 for crunching and 6.6.11 for downloading (for some reason 6.6.11 would randomly stop using the GPUs, but 6.4.5 always says high priority so would never download new WU).
--- End quote ---
6.6.11 has a bug that if a GPU job is running,and a 2nd GPU job with an earlier deadline arrives, neither job is executed ever. Maybe you get hit by this.
I use a script running in an infinite loop to notify me when this happens. Then a boinc restart fixes it... until next time. Also turning off "leave applications in memory while suspended" in your computing preferences seem to help a bit, but it doesn't solve it completely.
Kunin:
Sounds like it since it happens randomly. On days I work (12 hour shifts) I'm at my computer maybe 3-4 hours, so odds of me catching it is slim, hence I use 6.4.5 for crunching. I just switch to 6.6.11 to download 5-10 days cache, rebrand it all and then back to crunching.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version