From a24ac06cd5c208c5fb74af96f9430ff4b5682873 Mon Sep 17 00:00:00 2001 From: Radovan Pasek <radovan.pasek@vsb.cz> Date: Thu, 10 Apr 2025 11:06:20 +0200 Subject: [PATCH] Edit project-storage.md --- docs.it4i/storage/project-storage.md | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/docs.it4i/storage/project-storage.md b/docs.it4i/storage/project-storage.md index b8bb9cae..f97106f7 100644 --- a/docs.it4i/storage/project-storage.md +++ b/docs.it4i/storage/project-storage.md @@ -128,17 +128,11 @@ drwxrws---. 16 vop999 open-XX-XX 4096 led 20 16:36 2021-03-07-021446 ## Computing on PROJECT -!!!important "I/O Intensive Jobs" - Stage files for intensive I/O calculations onto the SCRATCH storage. +!!!important "I/O Jobs" + Stage files for I/O calculations onto the SCRATCH storage. -The PROJECT storage is not primarily intended for computing and it is strongly recommended to avoid using it directly for computing in majority of cases. - -On the other hand, the PROJECT storage is accessible from compute nodes and can be used for computing jobs with low I/O demands, -when copying data to other storage for computing is not feasible or efficient. -However, be aware of overloading the storage, as this will result in degraded performance for other users of the PROJECT storage or its unavailability. - -For maximum performance, you should always copy the files of I/O intensive jobs onto the SCRATCH storage. -The files should be copied to SCRATCH from Login nodes before submitting the job. +PROJECT storage is not designed for computational tasks and must not be used directly for such purposes. +Please ensure that all files are copied to SCRATCH from the login nodes before submitting your job. <! --- See also: data storage policy on filesystems (link?) --> -- GitLab