38,760
edits
Cloud/en: Difference between revisions
Updating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 6: | Line 6: | ||
Virtual machines can be easily replicated. One can take a "snapshot" of a VM which can then be started again elsewhere. This makes it easy to replicate or scale up a service, and to recover from (for example) a power interruption. | Virtual machines can be easily replicated. One can take a "snapshot" of a VM which can then be started again elsewhere. This makes it easy to replicate or scale up a service, and to recover from (for example) a power interruption. | ||
If you can fit your work easily into the [https://en.wikipedia.org/wiki/Supercomputer HPC] [https://en.wikipedia.org/wiki/Batch_processing batch] submission workflow and environment (see [[What is a scheduler?]]) it is preferable to work outside the cloud, as there are more [[National systems|resources available]] for HPC and software is already configured and installed for many common needs. There are also tools like [[ | If you can fit your work easily into the [https://en.wikipedia.org/wiki/Supercomputer HPC] [https://en.wikipedia.org/wiki/Batch_processing batch] submission workflow and environment (see [[What is a scheduler?]]) it is preferable to work outside the cloud, as there are more [[National systems|resources available]] for HPC and software is already configured and installed for many common needs. There are also tools like [[Apptainer]] to run custom software stacks inside containers within our HPC clusters. | ||
If your need isn't served by Singularity or HPC batch, then the cloud is your solution. | If your need isn't served by Singularity or HPC batch, then the cloud is your solution. | ||