Translations:Running jobs/106/en: Difference between revisions

Translations:Running jobs/106/en (view source)

349 bytes removed , 5 years ago

Importing a new version from external source

38,760

edits

Revision as of 14:18, 21 June 2018 (view source) FuzzyBot (talk \| contribs) (Importing a new version from external source) Tags: Mobile edit Mobile web edit ← Older edit		Revision as of 12:58, 9 April 2019 (view source) FuzzyBot (talk \| contribs) (Importing a new version from external source) Newer edit →
Line 1:		Line 1:
	Memory may be requested with <code>--mem-per-cpu</code> (memory per core) or <code>--mem</code> (memory per node). ~~We recommend that you specify memory in megabytes (e.g. 8000M) rather than gigabytes~~ (~~e.g. 8G~~)~~. In many circumstances specifying~~ memory ~~requests in thousands~~ of ~~megabytes~~ will ~~result in shorter queue wait times than specifying gigabytes~~. ~~For example, requesting <code>--mem=128G</code> (equivalent to 131072M) is more memory than is available for jobs on~~ nodes with a ~~nominal 128G . A job requesting <code>--mem=128G</code> qualifies for fewer nodes than one requesting <code>--mem=128000M</code>, and~~ is ~~therefore likely to wait longer. Similar reasoning also applies to <code>--mem-per-cpu</code> requests~~.		Memory may be requested with <code>--mem-per-cpu</code> (memory per core) or <code>--mem</code> (memory per node). On general-purpose (GP) clusters a default memory amount of 256 MB per core will be allocated unless you make some other request. At [[Niagara]] only whole nodes are allocated along with all available memory, so a memory specification is not required there.