Extending the OpenCHK Model with Advanced Checkpoint Features

TL;DR

This paper introduces compiler directives for application-level checkpoint/restart, simplifying programmability, enhancing flexibility, and supporting advanced features across different libraries without performance overhead.

Contribution

It proposes a unified, extensible programming model that simplifies checkpointing and supports advanced features, improving portability and reducing code complexity.

Findings

Significant reduction in code lines required for checkpointing.

No additional overhead introduced by the new directives.

Enhanced portability across different checkpoint libraries.

Abstract

One of the major challenges in using extreme scale systems efficiently is to mitigate the impact of faults. Application-level checkpoint/restart (CR) methods provide the best trade-off between productivity, robustness, and performance. There are many solutions implementing CR at the application level. They all provide advanced I/O capabilities to minimize the overhead introduced by CR. Nevertheless, there is still room for improvement in terms of programmability and flexibility, because end-users must manually serialize and deserialize application state using low-level APIs, modify the flow of the application to consider restarts, or rewrite CR code whenever the backend library changes. In this work, we propose a set of compiler directives and clauses that allow users to specify CR operations in a simple way. Our approach supports the common CR features provided by all the CR libraries. However, it can also be extended to support advanced features that are only available in some CR libraries, such as differential checkpointing, the use of HDF5 format, and the possibility of using fault-tolerance-dedicated threads. The result of our evaluation revealed a high increase in programmability. On average, we reduced the number of lines of code by 71%, 94%, and 64% for FTI, SCR, and VeloC, respectively, and no additional overhead was perceived using our solution compared to using the backend libraries directly. Finally, portability is enhanced because our programming model allows the use of any backend library without changing any code.