Skip to content

Commit 0fe07ff

Browse files
galfthanrkronberg
andauthored
Update usage-policy.md - quota and change to jobs (#2516)
* Update usage-policy.md - quota and change to jobs period 90 days for large projects (>5 TiB) No changes to jobs done * Update usage-policy.md * Update usage-policy.md * Update usage-policy.md --------- Co-authored-by: Rasmus Kronberg <43936697+rkronberg@users.noreply.github.com>
1 parent 9047a82 commit 0fe07ff

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

docs/computing/usage-policy.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,8 +53,9 @@ suitable disk systems.
5353
You can use the `csc-workspaces` command to see which cleaning cycle your
5454
projects are subject to.
5555

56-
A similar procedure will be introduced on Mahti, but it is not yet in place.
57-
The policy is still that users should keep only actively used data in scratch.
56+
**Mahti:** A similar procedure will be introduced on Mahti if the disk usage
57+
grows enough to warrant it. The policy is still that users should keep only
58+
actively used data in scratch.
5859

5960
## GPU nodes
6061

@@ -106,3 +107,10 @@ If you are still actively using the project you can gain access to the compute
106107
resources and storage by
107108
[applying](../accounts/how-to-apply-for-billing-units.md) for more billing
108109
units.
110+
111+
## Slurm job management by CSC
112+
113+
* CSC will not change job parameters like length or priority.
114+
* CSC can terminate jobs if they are misusing resources. E.g., if resources
115+
(CPU cores, GPUs, memory) are severely underutilized or IO is overloading
116+
the storage system.

0 commit comments

Comments
 (0)