| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: Standard check pointing value |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
fablefox
Senior Cruncher Joined: May 31, 2010 Post Count: 161 Status: Offline Project Badges: 
|
I think there is standard checkpoint value for each project mentioned:
----------------------------------------But first, let me explain. I know different pc have different speed, but there should be standard value. For example, a workunit take two hour on standard pc, on this pc, checkpointing is every 10 minutes. if the user notice that it will take four hour on the user pc, they will know that checkpoint happens every 20 minutes. Also, does app checkpoint evertime they can, or a good value they think it would be nice for the user? because users might have different opinion. for example the upload/download moment (for specific hours, always available). an app might choose to checkpoint every 20 minutes even though it actually can every 5 minutes. user might prefer 10. anyway, just a suggestion. from random clicking, i think for ebola the max time it took before checkpointing is around 15 min on my laptop (my preferences is that it always run. my work mostly uses putty to the server (so i work on server not my laptop so i don't mind). people who off their pc often / daily may prefer projects with short checkpointing, while people who run pc dedicated to wcg might prefer to choose project with longer checkpoint, because this does not effect them. my 2 cent. |
||
|
|
fablefox
Senior Cruncher Joined: May 31, 2010 Post Count: 161 Status: Offline Project Badges:
|
--edit--
----------------------------------------also like to add: checkpointing can be time based preference too. for example normal through out the day, and more frequent near end of day work and/or at night (where the possibility of switching off laptop/pc is real. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There have been projects that *can* checkpoint at small regular intervals, but most don't. They take a molecule, the algorithm tries to fit it into a slot/receptor/nook/crevice of the target, also measuring how much energy that takes... the lower the better. Since each mol has different properties/complexities, each fitting attempt can take longer or shorter [and is very difficult to resume/reconstruct, hence the drop backs to previous known good checkpoint if exited mid-run].
And No, checkpointing middle of a fit comes at a price, so it's not done unless it takes/could take really long. This was the case with OET, so much effort was taken to program 8, at 12.5% progress. The 12.5% can though be 30 seconds, but it can also be 60 minutes, and more. For CEP2 it was decided that any mid model analysis check-pointing was prohibitive... If you choose this science, you accept the conditions. For more write-up, visit the Start Here forum. There's a checkpoint topic. BTW, the BOINCTasks tool has a 'Suspend at next Checkpoint" select and right click feature. Set the OS to put the device to sleep when idle, which it detects when all jobs have completed theirs, and walk away. Best done with a zero buffer setting. |
||
|
|
|