Forum > Linux

SETI MB CUDA for Linux

<< < (66/162) > >>

riofl:

--- Quote from: sunu on 14 Aug 2009, 07:25:54 am ---
--- 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.

--- End quote ---

wow. never knew that... i dont see that in my system but that is because i run the cpugpu perl script often to catch random downloads so boinc gets restarted several times an hour.

soon as the scheduler gets fixed ill give the new one a shot :)

sunu:

--- Quote from: Kunin on 14 Aug 2009, 09:11:46 pm ---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.

--- End quote ---
Well, you could use a script to restart boinc automatically when the bug kicks in. I didn't do it because I didn't like too much complexity and at the end I preferred I have the control over boinc restart.


--- Quote from: riofl on 14 Aug 2009, 10:22:55 pm ---wow. never knew that... i dont see that in my system but that is because i run the cpugpu perl script often to catch random downloads so boinc gets restarted several times an hour.

--- End quote ---
Restarting boinc several times an hour surely squashed that bug.  :D


--- Quote from: riofl on 14 Aug 2009, 10:22:55 pm ---soon as the scheduler gets fixed ill give the new one a shot :)

--- End quote ---
Yesterday, some changes to the scheduler were introduced. The problems I posted above, it seems, were across all platforms as the changes were generic. The battle with task scheduling in boinc is an ongoing and never ending one.

I haven't checked boinc with the new changes to see how it runs. Feel free to check it. At last we'll have a "modern" boinc release with proper multi-gpu support in linux in the next round of "official" releases.

riofl:

--- Quote from: sunu on 15 Aug 2009, 04:55:42 am ---
Restarting boinc several times an hour surely squashed that bug.  :D

Yesterday, some changes to the scheduler were introduced. The problems I posted above, it seems, were across all platforms as the changes were generic. The battle with task scheduling in boinc is an ongoing and never ending one.

I haven't checked boinc with the new changes to see how it runs. Feel free to check it. At last we'll have a "modern" boinc release with proper multi-gpu support in linux in the next round of "official" releases.

--- End quote ---

what version is it? the latest i see in http://boincdl.ssl.berkeley.edu/dl/ is 6.6.37 or do i have to use svn and hope for the best? :P

sunu:

--- Quote from: riofl on 15 Aug 2009, 12:12:22 pm ---or do i have to use svn and hope for the best? :P

--- End quote ---

Yes, you have to compile from source.

riofl:

--- Quote from: sunu on 15 Aug 2009, 12:24:31 pm ---
--- Quote from: riofl on 15 Aug 2009, 12:12:22 pm ---or do i have to use svn and hope for the best? :P

--- End quote ---

Yes, you have to compile from source.

--- End quote ---

ok hope i got the right one. never did 'get' what to do with svn there are so many different sources. looks like the one i got was trunk 6.9.0. is that the correct one?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version