Message boards : Number crunching : Checkpoint interval
| Author | Message |
|---|---|
|
I have my GPU host set to "Write to disk at most every 300 seconds". Monitoring ACEMD2 6.11 with BoincTasks (which has a checkpoint counter/timer) I find that it is checkpointing approximately every 50 seconds, +/- the BT refresh rate of 3 seconds. | |
| ID: 18386 | Rating: 0 | rate:
| |
|
I suspect that setting applies to saving the boinc client state only, not to the applications (which have their own checkpointing mechanism) | |
| ID: 18388 | Rating: 0 | rate:
| |
|
Officially checkpointing of the scientific apps is the one thing this preference setting is meant for. Look in the unofficial Wiki | |
| ID: 18390 | Rating: 0 | rate:
| |
Officially checkpointing of the scientific apps is the one thing this preference setting is meant for. Look in the unofficial Wiki Exactly, TG. And with this in mind, I reiterate my question ;) (BTW, "unofficial" WIKI doesn't = "uninformed.") Some users, myself included, have found it useful to limit the amount of checkpointing certain application do, because this can improve their performance at the risk of losing more data in the event of a crash or deliberate restart. This is why Fred Melgert added the checkpoint counter/timer to his BoincTasks utility. ____________ | |
| ID: 18391 | Rating: 0 | rate:
| |
|
Our application does not take the value given by the BOINC client to checkpoint because for us it must be a multiple of the output file frequency. In this way all works nice when you stop and restart the application. | |
| ID: 18392 | Rating: 0 | rate:
| |
Our application does not take the value given by the BOINC client to checkpoint because for us it must be a multiple of the output file frequency. In this way all works nice when you stop and restart the application. OK gdf, thanks for the clarification :) ____________ | |
| ID: 18393 | Rating: 0 | rate:
| |
Message boards : Number crunching : Checkpoint interval










