| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: App ignoring preferences |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges: 
|
can u list your app_config.xml of WCG?!
---------------------------------------- |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Ok under computing preferences it said local, changed to web and 75% seems to have sorted it. Two remaining questions though : 1: why in the past did it work fine just by changing the number from 12 to 9? 2: I wonder why in computing preferences in the client it says its pulling the preferences from WCG site even though I have more than one project on the go? Last project where web prefs are modified are used -globally- for any client that is associated with that profile/location. Local prefs at point of save copies all web prefs at that point and changes anything you enter locally. These then become permanent for that client until the local prefs are cleared. Processors # entry on the web profiles is a legacy field. It only works [is supposed to only work] for client 6.2.28 and before [there commentary in the profile of WCG!]. All from 6.2.28 use the CPU processor %, so 75% on an 8 core is 6, on a 12 core 9 etc. Ignore the app_config question. The client config overrides processor selections in app_config. Latter just is a limiter per science app. 5+7 max concurrent will never become 12 running as 75% of 12 if overruling. Maybe you have something in cc_config in options, e.g. <ncpus> or something. If that is set to 16, then 75% becomes 12 :O). |
||
|
|
|