I'd say because the default job/scenario/use case is not long-lasting. Maybe it's somebody running an example, and you do not want to penalize default behaviour with checkpointing overhead?
My 2 cents. On Thu, Feb 7, 2013 at 11:16 PM, Sebastian Schelter <[email protected]> wrote: > Hi, > > I saw that checkpointing is disabled by default. I'd like to know (out > of scientific curiosity) why we decided to have this as default. > > Best, > Sebastian > -- Claudio Martella [email protected]
