Just because the user feels it is OK to checkpoint now does not mean that the application must checkpoint now. The application can certainly wait until it makes sense to checkpoint.
There are many applications that only get the opportunity to checkpoint occasionally. The client keeps the checkpoint flag turned on until a checkpoint actually occurs. jm7 |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Bernd Machenschalk <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Heinz-Bernd Eggenstein <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Cc: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |<[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |08/10/2012 08:38 AM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: [boinc_dev] Feature proposal: Safeguards against excessive checkpointing? | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Sent by: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |<[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| On 10.08.12 14:26, Heinz-Bernd Eggenstein wrote: > So what are the opinions here? Would it make sense to have something > either at BOINC API compile time > (e.g. -DBOINC_APP_MIN_CPT_INTERVAL=10) or on the C API level to enforce a > minimum checkpoint interval ? If this is really meant to be application specific, I wouldn't fix this at BOINC compile time. This would work for Einstein@Home as we currently build our Apps, but might not work so well for others. Instead I would keep this in boinc_api as a static variable (int min_checkpoint_period) and have a new API function (boinc_set_min_checkpoint_period(int)) to set it from the app. Best, Bernd _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
