Message boards : GPUs : CUDA Work Units do not Suspend when Computer in use
Message board moderation
Author | Message |
---|---|
Send message Joined: 8 Dec 11 Posts: 5 |
This problem is particular to Einstein@home. Seti@home suspends as soon as I move the mouse. Launching a 3D game with CUDA in use results in terrible performance and sometimes freeze/crash. I can quit the work units in Task Manager but I wonder if this could corrupt the work units and/or BOINC? I have checked my settings in the standard edition of BOINC Manager. CPU and CUDA are set to suspend when computer is in use. My Einstein@home preferences are set to run CUDA applications when available. Basicaly my system is: CPU: i7-860 GPU: nVidea GTX260 (2) in SLI Memory: 16GB PSU: 950 watts/1080 peak watts System: Windows 7 Pro 64 bit Firewall/Antivirus: Norton Security Suite |
Send message Joined: 5 Oct 06 Posts: 5129 |
Which version of BOINC are you running? 'Use GPU based on preferences' is a global setting, not per project. From what he says about SETI suspending, sounds like it's in operation already. Maybe there's something odd about the way Einstein's app does, or doesn't, respond to BOINC's "suspend" directive - but I haven't heard anything about that being a common Einstein problem. The Einstein message board would be the place to ask. |
Send message Joined: 8 Dec 11 Posts: 5 |
Which version of BOINC are you running? I'm running the current version I think, version 6.12.34 (X64). |
Send message Joined: 8 Dec 11 Posts: 5 |
Which version of BOINC are you running? Yes, I posted the same question there under my Einstein@home user name "Dogstar" I've got 47 views and no replies. Not even "Ageless" the moderator has replied. |
Send message Joined: 29 Aug 05 Posts: 15563 |
Yes, I posted the same question there under my Einstein@home user name "Dogstar" Probably because I am no moderator over there. That's Mike, Gary and Heinz, of the active ones and Kathryn and John of the lesser active ones. I didn't answer here, till now, because you're in good hands. Nothing to add. |
Send message Joined: 22 Jul 10 Posts: 36 |
I get the same "WU's do not Suspend"-type issue when running e.g., Moo! GPU tasks. It seems to me projects that update every X minutes/% ofsomethingorother behave quite badly when I need to do other [important-to-me] work Right Now irrespective of settings. In my case I have to manually intervene ... select & suspend all relevant tasks then restart (logoff is another option as is Shut Down) just to regain control of what my PC is to do next AKA:- KILL!!! Maybe I've got this wrong - if so advice is welcome. Meantine:- a polite note to (non-BOINC) project admins:- 60x60/24/7/365(+1/4) is an optional, nice-to-have modus operandi. Casual users who devote time to crunching off-peak do need the above-mentioned "KILL" behaviour. The difference between 0 and 1 is greater than the difference between 1 and 1,000,000,000 |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.