Waiting to run. Task checkpointing or maybe not.


log in

Advanced search

Questions and Answers : Windows : Waiting to run. Task checkpointing or maybe not.

Author Message
pinkpanther
Send message
Joined: 22 Jan 10
Posts: 56
Credit: 64,095
RAC: 0
Message 1461239 - Posted: 6 Jan 2014, 19:37:59 UTC
Last modified: 6 Jan 2014, 19:38:36 UTC

Just a little question for you.

But scratching my head, I really do not know the answer here.

If one or more task (at least when it comes to PrimeGrid tasks) becomes "Waiting to Run" in my task list, do these tasks reside in memory while doing so?

At least a task is supposed to regularly checkpoint to disk, but except for the usual restart of a task, including "Choosing Optimal Functions" for a Seti@home task, is there any difference except from that?

Thanks!

OzzFan
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13625
Credit: 31,050,399
RAC: 20,624
United States
Message 1461259 - Posted: 6 Jan 2014, 20:23:54 UTC - in response to Message 1461239.

That depends on what your preference is set to for:

Leave tasks in memory while suspended?
Suspended tasks will consume swap space if 'yes'

pinkpanther
Send message
Joined: 22 Jan 10
Posts: 56
Credit: 64,095
RAC: 0
Message 1461264 - Posted: 6 Jan 2014, 20:35:23 UTC
Last modified: 6 Jan 2014, 20:38:07 UTC

Using Boinc Manager 7.0.64, 32 bits, it is located under the Tools or similar pull down menu (national menu translation).

It is on the third pull down menu from the left where "Add/Remove project(s) / Account Manager" and "Options" are found at the top, making it the third choice there.

Under "Disk and Memory Usage", among other things, there is "Tasks checkpoints to disk at most every x seconds", where 60 seconds is the default value.

But that really is for running tasks, isn't it? If a task becomes "Waiting to Run", what happens then?

Is there any difference here at all?

The checkbox "Leave applications in memory while suspended" is unchecked.

This is as close as I am able to get here.

OzzFan
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13625
Credit: 31,050,399
RAC: 20,624
United States
Message 1461302 - Posted: 6 Jan 2014, 21:50:37 UTC - in response to Message 1461264.

You're right, tasks "Waiting to run" do not consume memory. You should be able to see all tasks and programs in memory using Windows' Task Manager.

pinkpanther
Send message
Joined: 22 Jan 10
Posts: 56
Credit: 64,095
RAC: 0
Message 1461309 - Posted: 6 Jan 2014, 22:23:12 UTC
Last modified: 6 Jan 2014, 22:24:51 UTC

Really, I was thinking a little about the validity and preservation of a given task itself, not necessarily about disk or memory consumption alone.

Running a .vlar task takes maybe taking 6-10 hours to complete. For a PrimeGrid Woodall task or any longer task, it may take 60 hours or maybe even 200 hours or more at times. If a task is waiting to run in memory and I turn of the computer in the meantime, the task should be resuming from the last checkpoint the task made to the disc.

It really becomes only a slight annoyance. I know from running some Woodall tasks that they are sensitive when it comes to the running environment. If a tasks is unable to start up from a checkpoint, it is likely that the end result may become completely wrong. Really, this all is just a small technical detail that really should be put out of the way.

Just curious, because I didn't have the answer to this question.

OzzFan
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13625
Credit: 31,050,399
RAC: 20,624
United States
Message 1461335 - Posted: 7 Jan 2014, 0:09:10 UTC - in response to Message 1461309.

Assuming there's nothing wrong with your RAM or your local storage (hard drive), SETI saves from the checkpoint to disk and always resumes correctly. I've yet to see an instance where a task "waiting to run" has not been able to validate.

pinkpanther
Send message
Joined: 22 Jan 10
Posts: 56
Credit: 64,095
RAC: 0
Message 1461341 - Posted: 7 Jan 2014, 0:20:14 UTC - in response to Message 1461335.

Thank you very much!

I think this problem has been solved.

Questions and Answers : Windows : Waiting to run. Task checkpointing or maybe not.

Copyright © 2014 University of California