checkpointing: consider allowing users to specify save frequency

[markmc]

In #222 we added a data checkpointing feature which has a "save frequency" parameter which tunes how often a checkpoint is saved.

Wed did not initially expose this to users because we felt the side effects of save_freq=1 - lots of files, some extra I/O - is not worth the extra user complexity of another command line parameter.

This issue tracks the need to consider this based on feedback and to decide whether we want to remove the parameter or expose it to users.

[github-actions]

This issue has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.

[bbrowning]

Still relevant, but we have some larger under the hood changes to SDG and will likely hold off on exposing more knobs for checkpointing until after those land.

[github-actions]

This issue has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.

[github-actions]

This issue has been automatically closed due to inactivity. Please feel free to reopen if you feel it is still relevant!