Thanks for the explanations. I just had a look and Einstein@Home did write a checkpoint exactly at the time when BOINC switched applications last. Currently, I'm running E@H and SETI only, so maybe I'm fine for now. I will have an eye on the checkpoint times though.
But usually, a checkpoint is written when switching without keeping the application in memory? It is regarded an error if a project does not do this, isn't it?
One would hope... but some (most?) simply don't. Likewise I would think that being told to quit, as in when BOINC is shut down, would checkpoint. But they don't appear to. I haven't tested it on every project, but I know at least two do not. Don't know about Einstein.
Einstein applications can checkpoint every time that the search moves to a new point on the sky. You can tell how often this happens by watching how often the RA or DEC values change on the screensaver (corresponding to how often the orange 'bullseye' moves). On typical machines this is once every few seconds. So Einstein can checkpoint as often as once every five or ten seconds.
Thanks for the explanations.
)
Thanks for the explanations. I just had a look and Einstein@Home did write a checkpoint exactly at the time when BOINC switched applications last. Currently, I'm running E@H and SETI only, so maybe I'm fine for now. I will have an eye on the checkpoint times though.
RE: RE: But usually, a
)
Einstein applications can checkpoint every time that the search moves to a new point on the sky. You can tell how often this happens by watching how often the RA or DEC values change on the screensaver (corresponding to how often the orange 'bullseye' moves). On typical machines this is once every few seconds. So Einstein can checkpoint as often as once every five or ten seconds.
Bruce
Director, Einstein@Home