aws-samples / aws-samples/hpc-cost-simulator

[BUG] LSF Parser not setting memory constraint correctly for multi-core jobs

Open
#47 0 comments 0 reactions 1 assignee Claimed by @cartalla View on GitHub
Dominant language
Python
Stars
14
Forks
5
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

In the LSF JOB_FINISH record the numProcessors is the number of compute slots requested and by default the memory request is per slot, NOT per job. The exception is if the span is set to multiple hosts in which case the number of cores.

Run experiments with jobs and different args and confirm the JOB_FINISH and jobs.csv values.

If the LSF job doesn't request memory then do not set it to the maximum amount of memory actually used.
The maximum amount of memory used is already in the ru_maxrss field of SchedulerJobInfo and is saved in the jobs.csv file.

The memory in rusage is in MB, not KB.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.