Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 8
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1301 times and has 7 replies Next Thread
William LeGro
Advanced Cruncher
Joined: Feb 26, 2009
Post Count: 99
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Tasks were running, now "waiting to run"

Haven't seen this before. I had 3 tasks running: Human Proteome (2) and Help Conquer Cancer (1). The HP tasks were 84% and 11% complete, the HCC was 71% complete when they just stopped, with the Status saying "waiting to run". No messages other than the usual download/starting etc., no error messages, no red fonts.

There are 3 others WCG tasks ready to start, and I also have 3 malariacontrol.net tasks running (they seem to run real fast) and 1 ready to start; and 1 climateprediction.net task running and 1 ready to start.

Why would those three tasks stop in the middle of running? With no message, no error? I don't know when they stopped, but today I joined malariacontrol.net and climateprediction.net and started tasking. Could they have interrupted my WCG tasks? And if so, why didn't the WCG tasks take precedence since they were already running?
----------------------------------------

[Feb 18, 2011 2:46:30 AM]   Link   Report threatening or abusive post: please login first  Go to top 
William LeGro
Advanced Cruncher
Joined: Feb 26, 2009
Post Count: 99
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Tasks were running, now "waiting to run"

Apropos of nothing (I think), just realized that the two climateprediction.net tasks are 170 HOURS long with completion dates in late May! Meanwhile, one malaria project has completed in less than a day and two others will finish tonight. All these are clicking along - a 4th malaria task has begun since I started writing this reply and is already 40% done - while the clock has stopped on all my WCG tasks.

If my computer capacity is playing a role, here is the profile:
iMac G5 3.06 GHz Intel Core i3
OS X 10.6.6
Memory: 4GB 1333 MHz DDR3
BOINC 6.10.58.
----------------------------------------

[Feb 18, 2011 2:57:56 AM]   Link   Report threatening or abusive post: please login first  Go to top 
William LeGro
Advanced Cruncher
Joined: Feb 26, 2009
Post Count: 99
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Tasks were running, now "waiting to run"

Well, I keep having to reply to my own post because I keep forgetting things. I have nothing much else running on this computer. I quit my browser (Firefox) and email, and have no other apps running, so aside from Finder (116 MB of memory) BOINC is the only program using any substantial amount of memory, and that's only in the high-30s MB out of 4GB. Also, one of the stopped tasks has resumed running, but the other two are still dormant.
----------------------------------------

[Feb 18, 2011 3:34:20 AM]   Link   Report threatening or abusive post: please login first  Go to top 
wplachy
Senior Cruncher
Joined: Sep 4, 2007
Post Count: 423
Status: Offline
Reply to this Post  Reply with Quote 
Re: Tasks were running, now "waiting to run"

"Waiting to Run" means the task was suspended (either manually or by the BOINC manager) to allow another task to run and then taken out of suspension. If you check the BOINC manager I'm sure you will see that all the cores are active. Without more detail it's hard to give the exact sequence but I'm guessing it's because the BOINC manager didn't think there was enough time to complete the "long" tasks if it waited for the HP and HCC tasks to finish, or it is because of your "switch bettwen applications" setting.

If you want to have them restart use the BOINC manager to suspend 3 of the running tasks and they will then restart.

Bill P
----------------------------------------
Bill P

[Feb 18, 2011 4:19:03 AM]   Link   Report threatening or abusive post: please login first  Go to top 
William LeGro
Advanced Cruncher
Joined: Feb 26, 2009
Post Count: 99
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Tasks were running, now "waiting to run"

Thanks. Suspending the running tasks did indeed restart the "waiting to run" tasks. It also made the running tasks I suspended go into "waiting to run" status, so to get them going I'd have to suspend the ones I just got restarted. This could go on, like, forever. Maybe when I'm bored, instead of playing solitaire, I could just play Suspend and Resume. ;-}

I've looked for an explanation of "switch between applications" that tells me what it means to raise or lower the number of minutes but I can't find one. I have mine set at 60 minutes, which I think was the default. What would happen if I entered "0" or "1000"? Is there any advantage to a lower or higher number? Since I don't use this computer for much of anything but web surfing, I'd like it to do as much good as possible, and it's capable of a lot more than I need it for.
----------------------------------------

[Feb 18, 2011 5:29:13 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Tasks were running, now "waiting to run"

3 projects means if keeping the Resource Share / Project Weight on default 100, each will get 1/3rd of the computing time. Then by default each 60 minutes or the nearest checkpoint to that, projects will be switched and those pre-empted put in "waiting to run" state. Better select Leave Application in Memory (LAIM) when running CEP2, as if a panic state develops, the science will be unloaded without waiting for a checkpoint.

So, want to finish jobs in 1 run... set the times to something like 600 minutes or whatever the longest run time is for your favourite science.

--//--

PS, setting it to 4300 minutes or higher will generally push most short deadline tasks to the front... same "waiting to run" will then occur too. The value depends also on the cache size value. And then the panic starts. Malaria has a short deadline, WCG has 10 days for most all... can result in Malaria processing much more work than it's fair share as the client will always try to have a task on hand to start, until the Long/Short Term Debt (LTD/STD) gets so negative that all fetching stops for that project and then the complaints appearing of "My client is not fetching work anymore for X Y or Z".

Crunching is simple until members start toying with the configurations without doing the (in)famous RTFM. (Read the Friendly Manual)

--//--
[Feb 18, 2011 10:09:53 AM]   Link   Report threatening or abusive post: please login first  Go to top 
William LeGro
Advanced Cruncher
Joined: Feb 26, 2009
Post Count: 99
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Tasks were running, now "waiting to run"

Thanks. Regarding the "friendly" manual (are you sure the F stands for friendly?), I've read plenty, understand less. If it's not in my "language" - that is, how my particular brain (and it is particular, sometimes weirdly so) processes what I read - I end up having to ask questions anyway. I'm just trying to get the most good work out of this computer.
----------------------------------------

[Feb 18, 2011 3:54:19 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Tasks were running, now "waiting to run"

All manuals, without exception, are with "friendly" intend, except those that were made using Yahoo-Babelfish to get them published in a non -native tongue. They do a product "unsell", subject to some comedians to hand some jollity around.

:-)
[Feb 18, 2011 4:10:43 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread