search

OSC / ondemand

Supercomputing. Seamlessly. Open, Interactive HPC Via the Web
https://openondemand.org/
MIT License
295 stars 107 forks source link

activejobs show max memory #1006

Open johrstrom opened 3 years ago

johrstrom commented 3 years ago

When this ticket in ood_core gets pulled in and release, activejobs should start using it.

https://github.com/OSC/ood_core/issues/256

Basically activejobs for slurm shows the minimum memory value for Memory when it likely should show maximum memory.

┆Issue is synchronized with this Asana task by Unito

johrstrom commented 3 years ago

When that issue on ood_core is complete it may return 0 for jobs that have the whole node. In this case the view should render that information (maybe in the form of "Entire Node"?) .

mcuma commented 3 years ago

I think "Entire node" is the easiest and reasonable solution.

We could try to extract the actual value by finding what node(s) the job runs on, and then parse the RealMemory from output of "scontrol show node ", but this would get more complicated if job used more nodes that could have different memory size (our nodes are not entirely homogeneous).

johrstrom commented 1 month ago

Probably need to take a look at all these fields and ensure they're correct for each scheduler.

Also related to memory field explicitly - maybe we just need a Minimum Memory and Maximum Memory rows.

Still want to get to this at some point (ood_core update is not complete at the time of writing).