Dear all, At E@H we have one app that (at least in the GPU variant) calls boinc_time_to_checkpoint() very frequently (more than once per second, far less frequently in the CPU version).
We noticed that for volunteers who changed the default checkpointing interval to something like, say,"1" or "0" sec, our app will as a consequence checkpoint every second. Per task...not nice on multicores :-) As this is a BOINC global setting and some projects (current or future) might actually for some weird reasons want to do it that way, I think there is no need to change the web interface or client. But I wonder whether there should be some convenient way in the API code (at runtime or compile time) to specify an override for a sensible minimum time interval between checkpoints based on the knowledge of the app developers, e.g. the cost of preparing and writing the chekpoint file. E.g. if the checkpointing is very expensive, you definitely don't want to checkpoint every second even if the volunteers *allow* you to do that. 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 ? I'd rather not deal with time stuff in the app code itself if BOINC can do that for me. P.S.: In addition, the general defaulting to (effectively) 1 sec checkpointing might be not a good idea in the current code. Maybe 60 seconds??? Ideas? Opinions? Thanks in advance HBE _______________________________________________ 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.
