| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Relatively new to this (June 2013).
Am running Seti@home as well as WCG projects on a Windows 7x64 I5. Cleared things out as advised before running upgrade and am running the BOINC 7.2.28 (x64) manager. No issues with that. It is probably something I am doing wrong in a profile (Local,Web, or both) BUT First, WCG projects will suspend running SETI projects and take over the task processing. This is especially true of FightAids@ projects. But, I might just notice this because of the abundance of tasks. In short, not playing nice with others. Secondly, the tasks chosen in the BONIC agent have nothing to do with their DUE DATE. Almost seems random. -- Since I keep about two or three days on hand and run 7x24, I finally had to suspend new tasks, suspend projects with later due dates, and run it for a day or so in order to avoid missing deadlines. Really don't want to micro-manage these things. Thank you in advance for any help. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
On your 'First', the v7 clients are designed to do block processing, meaning they'll do a period of one project [WCG is an ''umbrella project' seen by BOINC as 1], then the next, then the next. Assuming you have not changed the default resource shares [aka project weight], default 100, with WCG+SETI, that means over the longer haul, both will get approximately 50% of the FLOPS [An arbitrary way of measure through the Recent Earned Credit]. As soon as you start micromanaging tasks, BOINC get's confused, where's it's 'learning' cycle is about 14 days. Make a change and it will take another 14 days to even out. BOINC scheduling work based on the FIFO principle. With 2-3 days buffer there's a good chance you're already interfering with that principle, particularly if 'repair' tasks arrive that have a deadline that is smaller than 2 times buffer [3 days deadline divided by 2 is 1.5 days, meaning they might get rushed]. Then mostly FIFO is dropped and Earliest Deadline First kicks in. I will not argue over the voodoo in that process... I just 'know' and accept and keep my hands off and hold my buffers at a level that is lower than half of the shortest deadline work. Mostly processing with v7 is then FIFO. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks! Was the info I needed. Will make sure things are default and go with the flow.
|
||
|
|
|