Posts by old_user8176

1) Questions and Answers : Windows : Laptop losing work when client is shut down (Message 6093) Posted 14 Nov 2004 by old_user8176 Post: Hi crandles, Unfortuntely, suspending the client doesn't help when you are shutting the machine off. 5 to 15 minutes might not seem like much on an individual basis, but from a broad view of the whole project, this seems like a significant design oversight. If you take a low estimate and assume that 10% of all machines running BOINC CPDN experience a shutdown or interruption each day, with the current number of machines, you're looking at anywhere from 300 to 900 CPU hours lost <i>each day</i>. If you consider that this estimate might be higher, say 25%, this could reach upwards of 2000 CPU hours lost each day. That's a lot of work. I'm not trying to be difficult. As a long-time support of distributed computing projects (very long time), I'm just baffled as to why it was designed without some sort of state saving.
2) Questions and Answers : Windows : Laptop losing work when client is shut down (Message 6071) Posted 13 Nov 2004 by old_user8176 Post: Hi Trane, Thanks for your answer. I do manually exit BOINC in most cases, but it makes no difference to CPU time lost. I wonder if an admin could answer my question about saving state. It must be possible to save state when shutting down, and recover when starting back up. If I have to let me clients run for significant portions of time or risk losing all the work simply because I shut the client off, then I'm afraid that I won't be able to run this project. Couldn't this functionality be added in to a future version of BOINC?
3) Questions and Answers : Windows : Laptop losing work when client is shut down (Message 6068) Posted 12 Nov 2004 by old_user8176 Post: Hi, I\'ve read previous posts, etc, about this, but the issue is still unclear. I have a laptop which I run BOINC on, but it is often shut down or placed into hibernation. I have just noticed that my client is not progressing, and every time I boot it up the CPU time column shows the same value and my progress is reset. It\'s probably been doing this for months. Is there some way to get the client to save it\'s current state when it\'s shut down? This honestly should be a pretty basic function for any distributed project. Do I just have a bad work unit?