DMTCP: Distributed MultiThreaded CheckPointing

About DMTCP:

DMTCP (Distributed MultiThreaded Checkpointing) transparently checkpoints a single-host or distributed computation in user-space -- with no modifications to user code or to the O/S. It works on most Linux applications, including Python, Matlab, R, GUI desktops, MPI, etc. It is robust and widely used (on Sourceforge since 2007).

Among the applications supported by DMTCP are MPI (various implementations), OpenMP, MATLAB, Python, Perl, R, and many programming languages and shell scripting languages. With the use of TightVNC, it can also checkpoint and restart X-Window applications. The OpenGL library for 3D graphics is supported through a special plugin. It also has strong support for HPC (High Performance Computing) environments, including MPI, SLURM, InfiniBand, and other components. See for further details.

DMTCP supports the commonly used OFED API for InfiniBand, as well as its integration with various implementatoins of MPI, and resource managers (e.g., SLURM). See contrib/infiniband/README for more details.

News | See Also | Authors | Acknowledgement


We are currently looking for well qualified applicants who are interested in joining a Ph.D. program in order to do research on checkpointing and reversible debugging. Interested applicants should write to Gene Cooperman ( at Northeastern University.
[2015-10-15]: DMTCP 2.4.2 released!
This is a bug fix release. Some issues were fixed concerning: ./configure --enable-debug; compiling under clang; interval checkpointing (dmtcp_launch --interval); having dmtcp_launch --quiet pass on the --quiet flag when implicitly starting a new coordinator; when an application mmap's /dev/zero; improved support for sched_setaffinity() and friends; a report on tclsh-8.6 and its use of pthread_atfork(); on_semget() and semctl(); and a compilation error for SLES10.
[2015-09-02]: DMTCP 2.4.1 released!
This is primarily a bug fix release. It fixes an issue with version 2.4.0 and deleted shared memory files. In particular, this can affect the use of DMTCP with MPI in some circumstances.
[2015-07-24]: DMTCP 2.4.0 released!
This release provides better support for MPI/SLURM integration for Intel MPI, MVAPICH-2, MPICH-2, and Open MPI; glibc 2.21; and shared-memory segments. Check the release notes for more details.
[2014-07-14]: DMTCP 2.3.1 released!
This is primarily a bug fix release.
[2014-07-03]: DMTCP 2.3 released!
This is primarily a bug fix release. However, if you are using DMTCP for the ARM v7 CPU, or if you are using DMTCP either with the InfiniBand network or with the SLURM batch system, then it is strongly recommended to upgrade. Check the release notes for more details.
[2014-03-20]: DMTCP 2.2.1 released!
This is a bug fix release. Users relying on --enable-unique-checkpoint-filenames configure flag are highly recommended to upgrade to this release. Check the release notes for more details.
[2014-03-14]: DMTCP 2.2 released!
In this release, the lowest layers have been re-organized and partially re-written for greater clarity of code and greater maintainability. Also, users relying on the use of DMTCP with MPI, InfiniBand or the Toruqe or SLURM batch queues are strongly advised to upgrade. Check the release notes for more details.
[2014-01-12]: DMTCP 2.1 released!
This release includes enhancement to the core feature set and some newly stable plugins. Check the release notes for more details.
[2013-10-03]: DMTCP 2.0 released!
This version 2.0 release represents the future of DMTCP. DMTCP version 2.0 has been re-designed around the concept of plugins. The older DMTCP version 1.2.x branch will continue to be maintained for bug fixes. Check the release notes for more details.
DMTCP is currently maintained by Kapil Arya, Gene Cooperman, Rohan Garg, Jiajun Cao, and Artem Polyakov. The list of active developers continues to evolve.
The DMTCP project is partially supported by grants from Intel Corporation, and from the National Science Foundation under grant ACI-1440788. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of Intel Corporation or of the National Science Foundation.

Click here for comments. Logo