This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
cluster:147 [2016/03/29 17:36] hmeij07 |
cluster:147 [2017/05/24 18:32] hmeij07 [Files v0.2] |
||
---|---|---|---|
Line 4: | Line 4: | ||
==== BLCR Checkpoint in OL3 ==== | ==== BLCR Checkpoint in OL3 ==== | ||
- | * This page concerns SERIAL jobs only | + | * This page concerns SERIAL jobs only; SERIAL jobs can restart on any node |
* Installation and what it does [[cluster: | * Installation and what it does [[cluster: | ||
Line 14: | Line 14: | ||
Checkpointing is an expensive operation so do not checkpoint under 6 hours. For example, if your job runs for a month checkpoint once a day, if your job runs for a week checkpoint every 12 hours. From this point on I expect all users to checkpoint. Some software does this internally (Amber, Gaussian). For applications or home grown code you can use BLCR. (Too bad it does not work out of box within Openlava). | Checkpointing is an expensive operation so do not checkpoint under 6 hours. For example, if your job runs for a month checkpoint once a day, if your job runs for a week checkpoint every 12 hours. From this point on I expect all users to checkpoint. Some software does this internally (Amber, Gaussian). For applications or home grown code you can use BLCR. (Too bad it does not work out of box within Openlava). | ||
- | You need to test out checkpointing before you rely on it. I've notice that some local code, when opening files for output, BLCR does not notice it. The code below has such an example (file fid.txt). Hopefully future versions of BLCR will fix this. Or maybe we shuold | + | You need to test out checkpointing before you rely on it. I've notice that some local code, when opening files for output, BLCR does not notice it. The code below has such an example (file fid.txt). Hopefully future versions of BLCR will fix this. Or maybe we should |
BLCR, Berkely Lab Checkpoint and Restart, remembers file paths and process ids. The code stages the necessary STDOUT and STDERR files Openlava generates and invokes the relocation feature while ignore old process ids. If an application is large, and static, it is advisable to not save the application inside the checkpoint file. | BLCR, Berkely Lab Checkpoint and Restart, remembers file paths and process ids. The code stages the necessary STDOUT and STDERR files Openlava generates and invokes the relocation feature while ignore old process ids. If an application is large, and static, it is advisable to not save the application inside the checkpoint file. | ||
- | At the bottom of this page is the current version of '' | + | At the bottom of this page is the current version of '' |
* Here is an interactive simple sample run. | * Here is an interactive simple sample run. | ||
Line 45: | Line 45: | ||
Connection to petaltail lost. | Connection to petaltail lost. | ||
- | # that was not too clever, log back in, restart application in another directory | + | # ooops, |
[hmeij@petaltail 187]$ cd .. | [hmeij@petaltail 187]$ cd .. | ||
[hmeij@petaltail sanscratch]$ mkdir 188 | [hmeij@petaltail sanscratch]$ mkdir 188 | ||
Line 275: | Line 275: | ||
done | done | ||
+ | ==== Matlab ==== | ||
+ | |||
+ | * https:// | ||
</ | </ |