Search Mailing List Archives
[farmshare-discuss] maximum memory for an interactive job on Farmshare 2?
aseishas at stanford.edu
Tue Sep 5 14:48:22 PDT 2017
You can currently request up to the maximum amount of memory available on a given node, but large allocations may wait longer pending resources. In fact, it should not be possible to submit a job that violates scheduling policy; instead, the attempt will return and report an error like:
salloc: error: Job submit/allocate failed: Job violates accounting/QOS policy (job submit limit, user's size and/or time limits)
It’s also not possible to request a node configuration that cannot be fulfilled:
salloc: error: Job submit/allocate failed: Requested node configuration is not available
If you get a message stating that the job is “queued and waiting for resources” then the scheduler has it. The scheduler allocates resources as they become available according to each job’s priority. If you think your request may wait for awhile you can use the --mail-type and --mail-user options to receive e-mail notification when your job begins (see the man pages for sbatch, salloc, and srun for details), and once a job has been submitted you can use “squeue --start” to get an estimate of the start time.
Research Computing Specialist
Stanford | University IT
aseishas at stanford.edu<mailto:aseishas at stanford.edu> · 650.725.7490<tel:6507257490>
On Sep 1, 2017, at 7:17 AM, Jamie Or Brett <jbrett at stanford.edu<mailto:jbrett at stanford.edu>> wrote:
Hi Farmshare Discuss,
What is the maximum amount of memory we can request for interactive use? For example, I can't tell if it's impossible to request 50G memory or if I'm using the incorrect request command:
srun --pty --nodes=1 --time=00:01:00 --mem=50G --qos=interactive bash
With this, I end up in queue eternally.
farmshare-discuss mailing list
farmshare-discuss at lists.stanford.edu<mailto:farmshare-discuss at lists.stanford.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the farmshare-discuss