| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: One task at a time, or two at a time |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
z2000
Advanced Cruncher Joined: Feb 27, 2011 Post Count: 116 Status: Offline |
Thank you Lawrence and everyone.
----------------------------------------It's working now. I'm almost certain about the difficulty having to do with the insistence and persistence of the local Boinc settings, and also not fully understanding what 'run always' vs. 'run by preferences'? (which preferences?) So I did also tell the Boinc manager to use 50% of processors (but 100% of cpu time), and now the message states that it is indeed using the 'home' preference profile for this computer. My other two are on 'default' setting and I selected 'maximum output' here on site. This should allow whatever I need to do on this PC to run just fine, while allowing top speed computing for a WU and even completing them in almost half the time. I have an identical twin computer networked to this one, and that is running on Linux. I also have an ancient Dell with Linux which will run on most weekends. The one that is cable connected to this one is running two tasks, since I don't personally use that one much, and the 15% gain should be good.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Lawrence is right on the money, 'cept to add to the non-plus-ultra advise to stick to 2 cores is. to use a tool called ThreadMasterGUI [See FAQs]. With a P4-HT you can then tune the different sciences to a load max, just enough to get sufficient user responsiveness. This way you'll be able to return more work. Only time you'd need to revisit TM is when a new science version is out or added to the selection.
Many scheduling and crunching prefs only work when "Run based on preferences" ** is selected on the Activity menu and once you've entered a single local pref, they override the website prefs until you hit the 'Clear' button in the BM prefs screen. Really, the client first reads in the web prefs, 'home' in your case, and then the local prefs. A few web prefs are still not in the local prefs, which is why they're read in that order. ** Selecting the allowed number of cores is one of those that is always in effect, no matter the *Run...* option. Same goes for all Disk/Memory controls. Anything in terms of *conditionally* reducing crunching is active when the '... based on prefs'' is ticked as a broad rule. --//-- |
||
|
|
|