From 075dfc0e8ba84d7d24fd7754006dc3d94be2de0a Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Mon, 7 Oct 2024 14:08:34 +0200
Subject: [PATCH] Update content
- Remove outdated note on SSD storage
- Refine note on node-local storage
---
doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md
index 695b6269a..e20e5a9ef 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md
@@ -38,10 +38,10 @@ filesystems.
[workspace](workspaces.md).
* For data that seldom changes but consumes a lot of space, the
[`walrus` filesystem](working.md) can be used.
- * **SSD**, in its turn, is the fastest available filesystem made only for large parallel
- applications running with millions of small I/O (input, output operations).
- * If the batch job needs a directory for temporary data then **SSD** is a good choice as well.
- The data can be deleted afterwards.
+ * If your batch job needs a directory for temporary data then node-local storage (`/tmp`) is
+ a good choice. The data will be deleted when the job has finished. The subsection
+ [Node-Local Storage in Jobs](/slurm/#node-local-storage-in-jobs) holds valuable information on
+ this topic.
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
--
GitLab