| 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: 43
|
|
| Author |
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
@Uplinger: Please consider upping the limit for max no of tasks outstanding per core, currently set at 25. I think that limit was set at a time when the length of FAHV WUs was very unpredictable, the average length was longer, and occasionally this was causing WUs to miss their return deadline. Now there will be no more for a while of the faah WUs to pad out the cache length, and FAHV WUs are much shorter and much better-behaved, so the limit makes a joke of the work cache setting in our BOINC clients. At the start of yesterday's outage, my machines were maxed out on WUs per core but some machines started running out of work after only about 14 hours. FYI, I have increased the the max from 25 to 35. I'm hesitant to increase it further because OET1 is not able to be sized. Also, we are looking into increasing the runtime for FAHV which should help keep your machines busy. Thanks, -Uplinger |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges:
|
Please do increase the runtime for FAHV.
----------------------------------------Combine 3 or so workunits into one (if possible). ![]() - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Work units are not combined for FAHV, it's how many dockings being packaged in one job, the max being 250 IIRC, but that could be a AutoDock number. Realize the runtime effect on Android pretty please if 3x... It's why they were cut relatively short, to accommodate the platform.
|
||
|
|
|