| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: Much Longer WUs |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 61
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
They seem to be getting much longer.............
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yup, just had two w/units of over 19hrs, both from FAAH 'LEDGB' sequence. On the other hand got about 540 points for each, so no worries.
---------------------------------------- [Edit 1 times, last edit by Former Member at Sep 8, 2014 7:57:00 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just another thread on longer / shorter, in the mcm forum! That's what they do.
Don't care, but it upsets the agent. The buffer doubled in projected runtime hours with 1.5 days set, but now computed as taking near 3 days. This causes repair tasks to now run in high priority. Those 'waiting and watching' for wingmen to get credited will be happy |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1304 Status: Offline Project Badges: 
|
I think you may have the wrong thread Douglas. The longest MCM task that I have had is about 7.87 hours batch 7317 but tasks are currently down around 2 1/2 hours batch 7378
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Guilty as charged, Speedy51.
Was not concentrating whilst posting the comment. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I currently have about 100 tasks queued with time estimates of around three hours. These are all due within a week. The tasks are averaging over ten hours each, resulting in the queue getting behind, and bumping their priority to high, thereby evicting my other projects from their scheduled runtime. Due to your estimation error, new tasks keep arriving faster than they should be being processed, so there is no let-up. Please fix!
|
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges: 
|
Hi Kevin,
----------------------------------------The quick fix from your side should include deleting, let say, 50 unstarted tasks and setting cache to, let say, 2.5 days. This might prevent similar situation would occure in the future. Cheers   Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006  [Edit 1 times, last edit by branjo at Sep 26, 2014 8:56:08 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yeah -- I'd already decreased the cache to 2.1 days (from 4) but new tasks just kept arriving about as fast as the old ones were completed... [sigh]
I don't mind, as long as it will eventually come right. I'll give it another week to settle down... |
||
|
|
l_mckeon
Senior Cruncher Joined: Oct 20, 2007 Post Count: 439 Status: Offline Project Badges:
|
I've gotten into the habit of running one of each day's batch of tasks to the first checkpoint (10 minutes), just to get a realistic idea of how long they all may take to complete.
BOINC Manager's Progress reading is reasonably accurate, although it initially overestimates the time required by 10% to 15%. |
||
|
|
darkwinguk
Cruncher Joined: Nov 5, 2005 Post Count: 6 Status: Offline Project Badges: 
|
I don't know whether it's my computer, but I currently have a task where it's taken an hour of CPU time to do 9%, but BOINC reckons only 3 and a half hours to completion.
The FAAH project is even worse, having taken 4 hours to do 6%, but it reckons it'll be done in 21 minutes... I basically stop the projects from sending me any new tasks until I'm sure the time to completion is accurate - otherwise it sends me new tasks when I have "30 mins" left to go, when clearly I have many hours. |
||
|
|
|