Comparison to other CR projects - Revision history

Sergey Bronnikov: added absent architectures for criu

2015-12-09T19:20:56Z

added absent architectures for criu

Kir: added openvz, renamed other to CKPT

2015-07-23T20:34:05Z

added openvz, renamed other to CKPT

Cov: /* (In-Kernel) Linux Checkpoint/Restart */

2015-07-23T12:13:52Z

(In-Kernel) Linux Checkpoint/Restart

Cov at 12:13, 23 July 2015

2015-07-23T12:13:25Z

Kir: /* CRIU, DMTCP, BLCR, OpenVZ comparison table */ link to What can change after C/R

2015-04-08T21:32:17Z

CRIU, DMTCP, BLCR, OpenVZ comparison table: link to What can change after C/R

Kir: /* CRIU, DMTCP, BLCR, OpenVZ comparison table */ link to memory changes tracking

2015-04-08T16:07:19Z

CRIU, DMTCP, BLCR, OpenVZ comparison table: link to memory changes tracking

Kir: /* CRIU, DMTCP, BLCR, OpenVZ comparison table */ finish converting to template:yes, template:no etc

2015-04-08T16:05:14Z

CRIU, DMTCP, BLCR, OpenVZ comparison table: finish converting to template:yes, template:no etc

Show changes

Kir: /* CRIU, DMTCP, BLCR, OpenVZ comparison table */ start using Yes/No templates

2015-04-08T15:54:02Z

CRIU, DMTCP, BLCR, OpenVZ comparison table: start using Yes/No templates

Kir: removed links from headings (looks bad/redundant)

2015-04-08T15:24:44Z

removed links from headings (looks bad/redundant)

Kir: optimized words to spaces ratio ;)

2015-04-08T15:22:59Z

optimized words to spaces ratio ;)

@@ Line 48: / Line 48: @@
 |-
 | Arch
-| x86_64, ARM
+| x86_64, ARM, AArch64, PPC64le
 | x86, x86_64, ARM
 | x86, x86_64, PPC/PPC64, ARM

@@ Line 23: / Line 23: @@
 Both tools appear primarily focused on reducing benchmark runtime on slow computer architecture simulators, leveraging sampling algorithms such as SimPoint.
-== (In-Kernel) Linux Checkpoint/Restart ==
+== OpenVZ (in-kernel) ==
 (In-kernel) [https://ckpt.wiki.kernel.org/index.php/Main_Page Linux Checkpoint/Restart] was a project from around 2008 to around 2010 to implement checkpoint/restart of Linux processes.

@@ Line 25: / Line 25: @@
 == (In-Kernel) Linux Checkpoint/Restart ==
-(In-kernel) [https://ckpt.wiki.kernel.org/index.php/Main_Page Linux Checkpoint/Restart] was a project from around 2008 to around 2010 to implemented checkpoint/restart of Linux processes.
+(In-kernel) [https://ckpt.wiki.kernel.org/index.php/Main_Page Linux Checkpoint/Restart] was a project from around 2008 to around 2010 to implement checkpoint/restart of Linux processes.
 == CRIU, DMTCP, BLCR, OpenVZ comparison table ==

← Older revision		Revision as of 12:13, 23 July 2015
Line 22:		Line 22:

	Both tools appear primarily focused on reducing benchmark runtime on slow computer architecture simulators, leveraging sampling algorithms such as SimPoint.		Both tools appear primarily focused on reducing benchmark runtime on slow computer architecture simulators, leveraging sampling algorithms such as SimPoint.
		+
		+	== (In-Kernel) Linux Checkpoint/Restart ==
		+
		+	(In-kernel) [https://ckpt.wiki.kernel.org/index.php/Main_Page Linux Checkpoint/Restart] was a project from around 2008 to around 2010 to implemented checkpoint/restart of Linux processes.

	== CRIU, DMTCP, BLCR, OpenVZ comparison table ==		== CRIU, DMTCP, BLCR, OpenVZ comparison table ==

@@ Line 89: / Line 89: @@
 |-
 | Retains behavior of the c/r-ed programs?
-| {{Yes}}
+| {{Yes}} (but see [[What can change after C/R]])
 | {{No}}, because of wrappers on system calls
 | {{No}}, because of wrappers on system calls

@@ Line 96: / Line 96: @@
 |-
 | Live migration
-| {{Yes}}, even if kernel, libs, etc are newer. Can use Memory Changes Tracking to decrease freeze time
+| {{Yes}}, even if kernel, libs, etc are newer. Can use [[memory changes tracking]] to decrease freeze time
 | {{Yes}}, if both kernels are recent
 | {{Yes}}, but if all components are the same. Even if prelinked addresses are different, it will not restore, but it can save the whole used libs and localization files to restore program on the different machine

@@ Line 53: / Line 53: @@
 |-
-| Need in modified kernel
+| Uses standard kernel?
-| No, provided it's 3.11 and above
+| {{Yes}}, provided it's 3.11 or later
-| No
+| {{Yes}}
-| No, just need to load module. May be problems with installation on new kernels
+| {{Yes}}, just needs to load module
-| Yes
+| {{No}}. OpenVZ kernel is required
 |-
-| App need to pre-load special libraries
+| Can be used without preloading special libraries before app start?
-| No
+| {{Yes}}
-| Yes
+| {{No}}
-| Yes
+| {{No}}
-| No
+| {{Yes}}
 |-
-| Requires root privileges
+| Can be used as non-root user?
-| No, but user can only manipulate tasks belonging to him
+| {{Yes}}, but user can only manipulate tasks belonging to him
-| No
+| {{Yes}}
-| No
+| {{Yes}}
-| Yes
+| {{No}}
 |-
-| Need to modify programs to C/R
+| Can run unmodified programs?
-| No
+| {{Yes}}
-| No
+| {{Yes}}
-| Yes. There are some difficulties with statically linked applications, and with LinuxThreads (it does not support them at all)
+| {{No}}. Statically linked and/or threaded apps are unsupported.
-| No
+| {{Yes}}
 |-
-| Need to prepare tasks
+| Can run unprepared tasks?
-| No
+| {{Yes}}
-| Yes. It preloads the DMTCP library. That library runs before the routine main(). It creates a second thread. The checkpoint thread then creates a socket to the DMTCP coordinator and registers itself. The checkpoint thread also creates a signal handler.
+| {{No}}. It preloads the DMTCP library. That library runs before the routine main(). It creates a second thread. The checkpoint thread then creates a socket to the DMTCP coordinator and registers itself. The checkpoint thread also creates a signal handler.
-| Yes. CR shall notify processes when a checkpoint is to occur (before the kernel takes a checkpoint) to allow the processes to prepare itself accordingly.
+| {{No}}. CR shall notify processes when a checkpoint is to occur (before the kernel takes a checkpoint) to allow the processes to prepare itself accordingly.
-| No
+| {{Yes}}
 |-
-| Does it change behavior of the c/r-ed programs?
+| Retains behavior of the c/r-ed programs?
-| No
+| {{Yes}}
-| Yes, because of wrappers on system calls
+| {{No}}, because of wrappers on system calls
-| Yes, because of wrappers on system calls
+| {{No}}, because of wrappers on system calls
-| No
+| {{Yes}}
 |-
 | Live migration
-| Yes, even if kernel, libs, etc are newer. Can use Memory Changes Tracking to decrease freeze time
+| {{Yes}}, even if kernel, libs, etc are newer. Can use Memory Changes Tracking to decrease freeze time
-| Yes, if both kernels are recent
+| {{Yes}}, if both kernels are recent
-| Yes, but if all components are the same. Even if prelinked addresses are different,it will not restore, but it can save the whole used libs and localization files to restore program on the different machine
+| {{Yes}}, but if all components are the same. Even if prelinked addresses are different, it will not restore, but it can save the whole used libs and localization files to restore program on the different machine
-| Yes
+| {{Yes}}
 |-
 | Containers
-| Yes, LXC and OpenVZ containers
+| {{Yes}}, LXC and OpenVZ containers
-| No. It doesn't support namespaces, so it probably can’t dump containers
+| {{No}}. It doesn't support namespaces, so it probably can’t dump containers
-| Looks like no
+| {{No|Looks like no}}
-| Yes
+| {{Yes}}
 |-

@@ Line 1: / Line 1: @@
 This pages tries to explain differences between CRIU and other C/R solutions.
-== [http://dmtcp.sourceforge.net DMTCP] ==
+== DMTCP ==
 {{:DMTCP}}
-== [https://ftg.lbl.gov/projects/CheckpointRestart BLCR] ==
+== BLCR ==
 Berkeley Lab Checkpoint/Restart (BLCR) is a part of the Scalable Systems Software Suite ,
@@ Line 23: / Line 23: @@
 Both tools appear primarily focused on reducing benchmark runtime on slow computer architecture simulators, leveraging sampling algorithms such as SimPoint.
-== [http://criu.org CRIU], [http://dmtcp.sourceforge.net DMTCP], [https://ftg.lbl.gov/projects/CheckpointRestart BLCR], [https://openvz.org OpenVZ] ==
+== CRIU, DMTCP, BLCR, OpenVZ comparison table ==
 “looks\seems like yes/no” - i found only unproved message(s) saying “yes”/“no”