Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: max-memory assumes bytes instead of megabytes #79

Open
fgvieira opened this issue Jun 25, 2021 · 0 comments
Open

Bug: max-memory assumes bytes instead of megabytes #79

fgvieira opened this issue Jun 25, 2021 · 0 comments

Comments

@fgvieira
Copy link

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.

@fgvieira fgvieira changed the title max-memory assumes bytes instead of megabytes Bug: max-memory assumes bytes instead of megabytes Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant