User Tools
enforcing_memory_allocation
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
enforcing_memory_allocation [2022/01/26 10:03] root |
enforcing_memory_allocation [2022/01/26 10:04] (current) root |
||
|---|---|---|---|
| Line 21: | Line 21: | ||
| </ | </ | ||
| - | If you have previously run jobs on the old cluster, you can find out how much memory they used by using the **sacct** command. You can either find the job id of a completed job on the old cluster (perhaps from the slurm-NNNNNN.out file name) and then run a command like this: | + | If you have no idea how much memory your job will use, but are convinced that it will use more than the default amount (8GB per core allocated to the job), then you should run at least one test case using the **--exclusive** option and the " |
| + | |||
| + | If you have previously run jobs on the old cluster | ||
| < | < | ||
| Line 35: | Line 37: | ||
| The output of this command could be parsed to get the maximum amount of memory used by this particular type of job). (If you use the same script name for multiple different jobs, this will mix them up.) | The output of this command could be parsed to get the maximum amount of memory used by this particular type of job). (If you use the same script name for multiple different jobs, this will mix them up.) | ||
| - | If you have no idea how much memory your job will use, but are convinced that it will use more than the default amount (8GB per core allocated to the job), then you should run at least one test case using the **--exclusive** option and the " | ||
enforcing_memory_allocation.1643209427.txt.gz · Last modified: 2022/01/26 10:03 by root
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
