| 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 |
|
|
DCS1955
Veteran Cruncher USA Joined: May 24, 2016 Post Count: 668 Status: Offline Project Badges:
|
Today I had a WU come up with a "Waiting to Run" status vs Ready to Run. It had a paused Progress of 1%. A new HSTB WU slipped in a completion date less than the usual 10 days in future. I was happy to get that HSTB but overall looked strange. Obviously some sort of WCG weirdness I have not seen before.
----------------------------------------![]() ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Much scheduling weirdness starts if there is too much work cached relative to the actual daily up-time. Usually the tipping point is when any deadline is less than twice the buffer completion size. For example, if a deadline is 2 days and the buffer is 1.25 days, the 2 day job gets prioritization. If you only run WCG, then with that "waiting to run" another job is "running high priority". See this all the time when FAH2 jobs arrive in the mix.
----------------------------------------[Edit 1 times, last edit by Former Member at Mar 12, 2019 10:12:35 AM] |
||
|
|
DCS1955
Veteran Cruncher USA Joined: May 24, 2016 Post Count: 668 Status: Offline Project Badges:
|
TY
----------------------------------------![]() ![]() |
||
|
|
|