Skip to content

more detailed definition of task constraints (memory, cputime) #76

@jkrue

Description

@jkrue

We have to enhance the task specification for memory and cpu time ? For now it is unclear if given constraints limits the task for all requested cores or just for a single one. My "natural" understanding (limitation aims the whole task) could be complete different from another user (e.g. limitation aims a single core).

example :

{
  "user" : "bibiserv",
  "cores" : 32,
  "memory" : 120,
  "cputime" : 10,
  "stdout" : "/vol/.../bibiserv2_2016-07-13_122031_Ts5W6",
  "stderr" : "/vol/.../bibiserv2_2016-07-13_122031_Ts5W6",
  "cmd" : "/vol/.../bibiserv2_2016-07-13_122031_Ts5W6/BatchFile_751909506511939005.sh",
  "container" : null
}

For my understanding the whole task needs 32 core to run and is limited to 120 GB memory and 10 hour cpu time. A typically grid engine user understands the above definition as memory limitation per core (3840 GB = 32 * 120 GB) and cpu time limitation for the whole task.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions