| 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 |
|
|
bfmorse
Senior Cruncher US Joined: Jul 26, 2009 Post Count: 442 Status: Offline Project Badges:
|
I am trying to determine HOW the BOINC application decides which WU to process next in and amongst those waiting to start.
Does anyone have any reference information or knowledge of how that happens? Thanks. |
||
|
|
HyperComputing
Advanced Cruncher Joined: Aug 10, 2019 Post Count: 74 Status: Offline Project Badges:
|
The most logical should be in the download order.
----------------------------------------When a WU is downloaded boinc gives it a deadline for execution. Depending on the type of WU this date may be longer or shorter. Boinc then averages between the execution deadline and the estimated duration of this execution to determine if a WU should take priority over the others. WUs whose date is almost reached take priority. Sometimes, after finishing an ARP for example, boinc recalculates the deadlines and certain WUs take priority. The estimated execution time is usually 2/3 longer than the actual execution time. All this of course is based on my own experience.
My GPU compute WUs as fast as I'm crushing bubble wrap.
|
||
|
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 786 Status: Offline Project Badges:
|
My understanding below, check the BOINC site for information.
----------------------------------------https://boinc.berkeley.edu/ The details likely change from oner release to another. Order depends on deadline (given by the project), long term debt of projects (calculated by BOINC client), priorities of projects (set by user on sites for projects) etc. Long term debt is calculated based on priorities and amount of work run for each project. If the client believes a task would be close to deadline by the time it ends based on estimated duration it will suspend another task to run it. When no tasks are in that position long term debt and arrival time determine order. Swap may occur based on user's chosen value in Switch between applications every: x minutes, may be at a checkpoint. Paul.
Paul.
|
||
|
|
|