tasks page shows waiting to run

socrbob
socrbob
Joined: 16 Feb 13
Posts: 19
Credit: 43863491
RAC: 3314
Topic 228358

Task page shows waiting to run, but elapsed shows 9:28:55 and remaining shows ---. Application  is gamma-ray pulsar search #5.11 (FGRPSSE) and name is LATeah10894_1416.04556520_0.0_1. What can I do to get this corrected?

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5872
Credit: 117564473313
RAC: 35291795

socrbob wrote:... What can I

socrbob wrote:
... What can I do to get this corrected?

You could start by mentioning everything that you changed that must have caused this.  Without that information, all I can do is guess.

You have three computers registered.  By scanning the tasks lists for all of them, I was able to find the task you mention in this particular tasks list.  The one green (in progress) task on that page is the task in question.  You could have posted that link yourself to make it easier.

The computer is doing three different searches, 2 using the CPU and the 3rd using the GPU.  The crunch times indicate that the machine is quite capable but the number of CPU tasks completed per day is abysmal.  Either you rarely have your machine running or perhaps you have it set to pause CPU crunching whenever you are actively using your machine and then you turn it off as soon as you are finished.

As an example of why I make this assumption, consider that you only have that single FGRP5 task.  You received it on Oct 2 and it's still only (your figure) showing 9+hrs of crunch time some 11 days later. 

The real killer is what has happened with the other CPU search - Arecibo large.  You have eight in total.  1st was received on Oct 3 and returned Oct 8.  2nd was received on Oct 7 and returned on Oct 10.  Then comes the strange bit.  On Oct 11, you received 6 new tasks, all at once.  All still show as 'in progress'.

What changed to cause BOINC to request that many in one hit, when you only return one task every 3 to 5 days?  Your machine has 12 CPU cores.  Did you make a huge increase in your work cache size, for example?  Perhaps you dramatically (but temporarily) increased the number or cores allowed to crunch CPU tasks?  And then reversed it again?  Unless you tell the full story, who would know why you got that sudden burst of tasks, none of which have subsequently been returned?

The upshot of this seems to be that BOINC has suspended the FGRP5 task because it's now in panic mode trying to complete 6 Arecibo, large tasks before their deadline.  If that's the case (only you can see that) then the simple fix is to allow 6 CPU cores to run continuously to clear the backlog  Crunch time is only around 7 hrs per task.  The FGRP5 task will restart after BOINC gets out of panic mode.

All the above is guesswork because you don't give enough information to know for sure.  If you want a better answer you really need to mention all the details concerning your settings and how you use that machine.

Cheers,
Gary.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.