WT heck could this be correct or some frames are just shorter to work than others?
if it stays like this, this bad boy is smoking.
Min. Time / Frame : 00:26:40 - 126,141.8 PPD
Cur. Time / Frame : 00:28:04 - 111,843.2 PPD
R3F. Time / Frame : 00:27:53 - 112,642.7 PPD
Edit: Project ID: 8101
Edit2: NVM looking at the log I see it worked 4 frames in a row at shorter times & when back to as it was.
Since I edited this I'll add something I found that seems to help when shutting down the client.
At setup "this last time" I set my checkpoints to 3 mins. instead of every 15 mins. Now when stopping the client
and seeing the post on screen "stopping at next" don't recall just what it said but something to that nature.
Before when seeing this waring it would start back at 0% done, but only sometimes.
If I stop it now and see this I wait 3 to 4 mins before making any move or quitting Virtualbox & haven't seen the
problem where the WU starts over. Might just be luck that it hasn't, but thought it might be worth mentioning.
Shorter checkpoints on something that takes this long to do just seem like a better idea to me
This is how I use the 3 min. checkpoint. I start my client at the hour or half hour mark by the clock.
If for some reason I need to stop the client I wait until it finishes a frame then wait 3 to 4 mins after
that frame has finished before stopping the folding client "checkpoint written". Starting on a hour or
half hour point just make it much easier for me since I know it takes about 30 mins to work a frame
so if there is something I need to do I can be there waiting.
Better than having to wait 15 mins before shutting the client down to insure a checkpoint has been written.
Could this be the wrong way of thinking? So far its been working for me but would like to get others input
on setting a checkpoint time. How much does this cut into the folding time or does it effect it at all?
<message edited by TheWolf on Tuesday, August 14, 2012 3:15 PM>