| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Tasks switched to "Waiting to run" |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yesterday I had 20+ tasks running and most of then suddenly switched to "Waiting to run" in the middle of their progress and they still haven't switched back to running yet. Should this happen?
----------------------------------------The below link is a screenshot of what I'm seeing: https://www.dropbox.com/s/8obm1rfnsfchsry/WCG.PNG?dl=0 I can't be certain, but this seemed to happen when the tasks with 16CPU in their name started, or it could of been when I logged out and logged in again. [Edit 3 times, last edit by Former Member at Apr 30, 2020 10:29:13 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The event log is probably telling more as to the why. Suspecting those 16CPU tasks are multithreaded, thus grabbing all there is and causing WCG to be put on the backseat.
----------------------------------------Edit: Some of these multithreaded projects have an option in the device profile to define how many threads they're allowed to use. If not, app_config might have a way to do this with <avg_ncpus>n</avg_ncpus> the number of CPU instances (possibly fractional) used by the app version. If you so desire of course. [Edit 1 times, last edit by Former Member at Apr 30, 2020 10:39:46 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the quick reply.
----------------------------------------Yes, it definitely seems to be the 16CPU ones causing the issue. When one of them finally finished, a lot of the other tasks have resumed. I'm just surprised the Bionic client allows a new task to take over and delay existing tasks from finishing. [Edit 1 times, last edit by Former Member at Apr 30, 2020 2:16:10 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Could give you the TL;DR reply with some speculation on the timing or the short which is, eventually all will balance in the long run based on resource share each project was given in the device profiles, default 100.
----------------------------------------edit: spellcheck. [Edit 1 times, last edit by Former Member at Apr 30, 2020 2:35:03 PM] |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1406 Status: Offline Project Badges: 
|
I'm just surprised the Bionic client allows a new task to take over and delay existing tasks from finishing. When the REC (Recent Estimated Credit) is almost equal for your projects, BOINC will switch between the projects every 60 minutes. This is the default setting in your BOINC Manager's computing preferences: "Switch between tasks every .... minutes". To switch between projects after a task has finished set this to a much higher value e.g. 1440 (1 day) or even higher when your have very long running tasks. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The new 16CPU ones seem to be waiting in turn now as I would expect. Maybe it was because I suspended and resumed Bionics client at some point and rather than continuing with the existing ones it allowed new ones to start.
|
||
|
|
zaschf
Advanced Cruncher New Zealand Joined: Jan 28, 2009 Post Count: 61 Status: Offline Project Badges: 
|
Hi Andrew777,
----------------------------------------what you saw is not a 'maybe'. When you suspend tasks and other tasks start running as a result of that, the suspended tasks will not resume even though you selected that option until the running tasks are completed. I've used this 'feature' to get tasks ahead by suspending all and then resume the task(s) I want to run first.
Ubuntu 22.04.1 LTS [Linux 5.15.0-47-generic]
CPU: Intel Core i7-9700 @3.00GHz x 8 GPU: NVIDIA GeForce RTX2060 Rev. A plus a mighty Raspberry PI 4 |
||
|
|
|