Translations:Points de contrôle/1/en: Difference between revisions

← Older edit

Translations:Points de contrôle/1/en (view source)

Revision as of 14:23, 27 September 2024

11 bytes removed , 1 month ago

no edit summary

Rdickson

Bureaucrats, cc_docs_admin, cc_staff

2,879

edits

Revision as of 14:59, 21 August 2017 (view source) Stubbsda (talk \| contribs) No edit summary ← Older edit		Latest revision as of 14:23, 27 September 2024 (view source) Rdickson (talk \| contribs) No edit summary
Line 1:		Line 1:
	The execution time for a program is sometimes too long for the maximum duration of a job permitted by the job schedulers used on ~~Compute Canada~~ clusters. Long-running jobs are also subject to all of the risks of system instability due to power outages, hardware defects and so forth. A program with a short execution time can easily be restarted with little concern but for long-running software it is preferable to use checkpoints to minimize the risk of losing several days' worth of computation. These checkpoints take the form of binary disk files from which the program can be restarted at the point in the computation where the checkpoint file was initially created.		The execution time for a program is sometimes too long for the maximum duration of a job permitted by the job schedulers used on the clusters. Long-running jobs are also subject to all of the risks of system instability due to power outages, hardware defects and so forth. A program with a short execution time can easily be restarted with little concern but for long-running software it is preferable to use checkpoints to minimize the risk of losing several days' worth of computation. These checkpoints take the form of binary disk files from which the program can be restarted at the point in the computation where the checkpoint file was initially created.