You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using (at least) the torque adapter it seems that the memory is assumed to be in bytes, even though the help says that --max-memory is in megabytes.
I submitted a job asking for --max-memory 1024, and it shows as:
Req'd Req'd Elap
Job ID Username Queue Jobname SessID NDS TSK Memory Time S Time
----------------------- ----------- -------- ---------------- ------ ----- ------ --------- --------- - ---------
32678102 user batch job.reads_s 0 1 4 1024b 10:00:00 C --
Is --max-memory supposed to be in bytes or megabytes?
Either way, would it be possible to allow for suffixes? For example, to specify 1gb or 1024mb.
The text was updated successfully, but these errors were encountered:
fgvieira
changed the title
max-memory assumes bytes instead of megabytes
Bug: max-memory assumes bytes instead of megabytes
Jun 28, 2021
When using (at least) the
torque
adapter it seems that the memory is assumed to be in bytes, even though the help says that--max-memory
is in megabytes.I submitted a job asking for
--max-memory 1024
, and it shows as:Is
--max-memory
supposed to be in bytes or megabytes?Either way, would it be possible to allow for suffixes? For example, to specify
1gb
or1024mb
.The text was updated successfully, but these errors were encountered: