Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1284 times and has 3 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
6.10.58 Issues (Resolved)

Since I went from the older version to 6.10.58 I like some of the new features of it, but not being used yet is access to GPU processing.

Problems coming up.. sorry if these are known..

on one system the message log on a dual core box keeps saying CPU usage is too high and suspending.. can't see how when I have it set to max anyway with preferences. on another system with the same device profile settings with exepct for project selection the CPU errors don't occur, which is on a I7 but on that system which is less serious keeps looking for a GPU error comes all the time and there is none since it is a RDP controlled unit only..
----------------------------------------
[Edit 1 times, last edit by Former Member at Mar 17, 2011 1:35:09 PM]
[Mar 17, 2011 1:09:33 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: 6.10.58 Issues

Hi choj01,

The function of suspending computation can be disabled 2 ways:

1. Set the Local or Web Device Profile Preference "While Processor Usage Is Less Than ... "value from 25% to 0
2. Set the BOINC Manager activity menu to "Run always".

Let us know if you need more guidance.

--//--

edit: The client can be set via the cc_config.xml file to ignore all GPU detection / use with the <no_gpus>1</no_gpus> line in the <options> section. See: http://boinc.berkeley.edu/wiki/Cc_config.xml
----------------------------------------
[Edit 2 times, last edit by Former Member at Mar 17, 2011 1:23:39 PM]
[Mar 17, 2011 1:14:58 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: 6.10.58 Issues

I was looking that up actually and came back to change I found the issue nice this new version has a built in limiter for non BONIC work that will slow it down if non research goes up past 25% CPU seems like a built in CPU speed booster.. lol but the low priority setting in Device manager works just the same automatically.. any idea when the GPU features of the client will be used for WCG?
[Mar 17, 2011 1:33:42 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: 6.10.58 Issues

The WCG default for new members is actually 50%, but the Berkeley code has 25% out of the box. Even at 100% it kicks in at times, so put 0 as my pref. The yield latency of running tasks is as quick, the function created for those ''supersensitive'' that always see BOINC holding up even for a fraction ;-)

2011 was the plan for GPU... A pile of things have to be put in place to include hardware. It's not like flipping the switch. The server software is currently being upgraded, step by step to make sure nothing breaks.

--//--
[Mar 17, 2011 1:45:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread