Scheduling of the Spawning Processes
Pre-release
Pre-release
·
202 commits
to master
since this release
Features
- Kind of the evaluating virtual memory for the job is parameterized (origin process, heaviest spawned [sub]process, whole process tree of the origin)
By default the virtual memory is evaluated for the heaviest process in the process tree of the executing job.
It allows to use intermediate apps in the execution chain having valid memory constraints for the target app[s] that is assumed to the the heaviest. An example of job with intermediate process of time measuring (time) that is not considered in the vmem constrains for the job:
find_job = Job(args=('time', 'find', '/etc', '-name', 'sh'))Known Bugs
_LIMIT_WORKERS_RAMcauses huge degrade of the rescheduling performance when the worker processes meet the specified constraint- Jobs rescheduling with
_CHAINED_CONSTRAINTSdoes not kill jobs related to the terminated origin if they are in the terminating state with requested restart or are rescheduled because of the group violation of the memory constraints