| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Discovering Dengue Drugs - Together - Phase 2 Forum
Thread: New thread for It's raining Dengue, Hallelujah!... |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2370
|
|
| Author |
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges: 
|
Question: this morning I downloaded some DDDT2 WUs ... and a couple started immediately with the status "Running, high priority" and left the two WUs (also DDDT2) that were currently running in "Waiting to run" status. I'm not complaining... just curious why this is happening. Do some of the DDDT2 WUs have more priority than others?
----------------------------------------Thanks, CJSL |
||
|
|
BSD
Senior Cruncher Joined: Apr 27, 2011 Post Count: 224 Status: Offline |
Got a sprinkle or two on my non-DDDT2 dedicated devices in last few days. Thanks for the goodies.
 Turned out to be a good run for me. Didn't break any records but my 8 devices have been happy. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
cjslman, Not enough hours running in the day, or too high overall cache already with enough work in there with part that's due before your total cache can be completed, in the permitted run time. When, then BOINC tests the latest arrivals to see how long they will run. Certainly, if all cores/threads run Hi Priority, work fetching stops until the situation normalizes. How to return quickly to normal FIFO order is by reducing the cache/connect every xx settings and then sit it out, or abort excess to capacity work.
------------------------------------------//-- [Edit 1 times, last edit by Former Member at Jan 18, 2012 12:05:15 PM] |
||
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges:
|
Sekerob... so basically the BOINC client thinks that I have too much in my cache to process by the due date. OK, thanks for the explanation... I've placed my queue at a lower limit... and I'll keep crunching as fast as I can.
----------------------------------------Thanks, CJSL ---------------------------------------- [Edit 1 times, last edit by cjslman at Jan 18, 2012 2:16:28 PM] |
||
|
|
TXR13
Cruncher Canada Joined: Dec 5, 2005 Post Count: 36 Status: Offline Project Badges: 
|
Question: this morning I downloaded some DDDT2 WUs ... and a couple started immediately with the status "Running, high priority" and left the two WUs (also DDDT2) that were currently running in "Waiting to run" status. I'm not complaining... just curious why this is happening. This has happened to me a couple of times for a different reason than SekeRob mentioned. Three times now I've gotten repair units (ending in _2 instead of _0 or _1) for WUs where one of the wingmen errored out or detatched the client. Repair units have jumped immediately to the high priority queue, and regular FIFO processing resumes after the repair units clear the box. I have also experienced the effects of too large a queue, but in that case all running units suspended to run a different batch of regular (non-repair) units.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's many a reason why jumping queue happens [all in the RTFM], my first response mentioning that of the most frequent cause in context of what many are doing now with DDDT2 ;>)
Got the switch application time pumped or the cache above 3-4 days? Then the repairs will be put ahead in the queue too. Your client will have been remembered as being ''reliable'', returning tasks within 2 days, but that deprecates when running multiple days with returning results slower. --//-- |
||
|
|
mikey
Veteran Cruncher Joined: May 10, 2009 Post Count: 824 Status: Offline Project Badges:
|
I just changed several machines over to Dengue Phase 2 and 1 machine got lots of work, I set my cache to 1.5 days, but the 2nd machine got the message 'no work is available for Dengue'! It can't be over ALREADY can it?! I am still getting work so it is not yet over - from what I see (at b093 as of 90 mins ago) - about 60% of the work has been downloaded so there is still 40% to go. Either be patient or keep hitting the update button every 20 seconds until you get some work. Less than an hour after my post files started coming in, thanks!   |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3715 Status: Offline Project Badges:
|
Question: this morning I downloaded some DDDT2 WUs ... and a couple started immediately with the status "Running, high priority" and left the two WUs (also DDDT2) that were currently running in "Waiting to run" status. I'm not complaining... just curious why this is happening. Do some of the DDDT2 WUs have more priority than others? Were they ps ones, by chance?The ps-type WUs are distributed as if they were already repair WUs. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Interesting... done hundreds + what's in the buffers and none were of the 'ps' type.... and the map says these are A-Type. https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,28528
------------------------------------------//-- edit: prefix dg05? [Edit 1 times, last edit by Former Member at Jan 18, 2012 4:20:10 PM] |
||
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges:
|
I think that somehow BOINC thinks that I bit off more than I can chew. The "high priority" WUs are getting turned into "waiting to run" after a while and new "high priority" WUs are showing up. So I aborted aprox 20 hrs of WUs
---------------------------------------- to see if ANY of the WUs get finished (this has been a terrible day for crunching).As for them being 'ps' WUs, no I don't think so: dg05_ b275_ pqa004_ 1-- dg05_ b275_ pqa002_ 0-- CJSL |
||
|
|
|