Skip to content
Snippets Groups Projects
Commit 075dfc0e authored by Martin Schroschk's avatar Martin Schroschk
Browse files

Update content

- Remove outdated note on SSD storage
- Refine note on node-local storage
parent 69537b8e
No related branches found
No related tags found
2 merge requests!1138Automated merge from preview to main,!1134Review documentation w.r.t. filesystems and hardware
...@@ -38,10 +38,10 @@ filesystems. ...@@ -38,10 +38,10 @@ filesystems.
[workspace](workspaces.md). [workspace](workspaces.md).
* For data that seldom changes but consumes a lot of space, the * For data that seldom changes but consumes a lot of space, the
[`walrus` filesystem](working.md) can be used. [`walrus` filesystem](working.md) can be used.
* **SSD**, in its turn, is the fastest available filesystem made only for large parallel * If your batch job needs a directory for temporary data then node-local storage (`/tmp`) is
applications running with millions of small I/O (input, output operations). a good choice. The data will be deleted when the job has finished. The subsection
* If the batch job needs a directory for temporary data then **SSD** is a good choice as well. [Node-Local Storage in Jobs](/slurm/#node-local-storage-in-jobs) holds valuable information on
The data can be deleted afterwards. this topic.
Keep in mind that every workspace has a storage duration. Thus, be careful with the expire date Keep in mind that every workspace has a storage duration. Thus, be careful with the expire date
otherwise it could vanish. The core data of your project should be [backed up](#backup) and the most otherwise it could vanish. The core data of your project should be [backed up](#backup) and the most
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment