| 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: 12
|
|
| Author |
|
|
bieberj
Senior Cruncher United States Joined: Dec 2, 2004 Post Count: 406 Status: Offline Project Badges:
|
Wow - I remember my thinkpad running three of those work units that took between 50 to 90 hours to complete.
Good catch! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Everybody, knreed is completely correct. Although we had several hundred packages (i.e., groups of 1 to 2,000 docking jobs, with each job getting split into multiple different work units) waiting in the queue, these packages involved the use of a slightly different flavor of run parameters. These run parameters caused the estimated work unit duration to be about 40 hours/work unit, instead of the preferred 6 to 10 hours/work unit. This issue was noticed at the last possible moment. Consequently, I kicked it into high gear and burned the midnight oil on Thursday, Friday, and Saturday in order to re-create many new packages which use the run parameters that give the more consistent, shorter run times. The crisis was averted. Everything is fine now. The FightAIDSatHome queue is now full, and you shouldn't observe any more decreases in the dissemination of work units. Thank you all very much for your help, Dr. Alex Perryman Thank you for your efforts, well done. ![]() |
||
|
|
|