Whenever I restart BOINC, the running tasks are shown as restarting at 0. It has happened at least 3 times. It has never restarted at 0 on any of my win 7 machines. Am I missing something? I set it up just like on Win 7, expecting similar behavior, and didn't expect this. So: HELP! Please!
Copyright © 2024 Einstein@Home. All rights reserved.
Only thing I can think of is
)
Only thing I can think of is that I didn't let it run long enough to take any checkpoints...what is the default setting for that?
Thanks!
Likr Roseanne Rosanadanna
)
Likr Roseanne Rosanadanna says, "Nevermind". The checkpoints occur starting around 50 minutes or so - my bad. Sorry!
Just for the benefit of
)
Just for the benefit of anyone else reading this thread and wondering ....
It's very hard for anyone to help with a problem if you give no details. As a bare minimum, it would have been helpful if you linked to the host in question (you have 5 so which one) and you mentioned the particular search and app that seemed to be not writing checkpoints.
I know the GPU apps write checkpoints quite regularly (if you haven't changed the default settings to some incredibly long time span) so I'm guessing you may have been referring to the GRP search using CPUs which tends to have a longer interval, particularly if you have a slow CPU.
However, 50 mins seems way too long so I would suggest you check what you have for the setting that allows you to delay checkpoints. You find the setting under account -> preferences -> computing and you use the 'Advanced' dropdown to look at a whole swag of knobs you could play with. The one you need is "Request tasks to checkpoint at most every: ___ seconds". The default is 60 secs but, because it's an 'at most' setting, the actual interval will be longer if the app is not designed to checkpoint that frequently.
If your estimate of "50 mins" is accurate, you may have an inappropriately large value for that setting, so you should check it out.
If the setting is still at the default value, it's possible that you have a CPU task that's not designed to checkpoint frequently. I don't run CPU tasks so I don't know if that might be happening at the moment. In the distant past, there were times when checkpoint frequency was rather longer than usual. Maybe that's happening again. To make sure you don't lose a lot of progress if a CPU task gets suspended, there is a setting for keeping tasks in memory when suspended. It's a good idea to make sure that setting is 'on'. If it's not on, a suspended CPU task has to use the last saved checkpoint when it resumes and some progress will be lost.
Cheers,
Gary.
... he only has one WIN10 rig
)
... he only has one WIN10 rig ...
San-Fernando-Valley
)
But the issue of making sure the checkpoints are set for minute or 4 minutes is very important.
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor)
RE that parameter:
)
RE that parameter: Checkpoints are at the default of "at most" 60 secs, I never played with it.
Either in my account or in BOINC mgr
... that was a hint as to
)
... that was a hint as to which rig he meant ...
Regards