Scheduling

Showing 37

json output for "badmin lsfproxyd status"

The new solution LSFProxyd does not dump status in json file. This RFE is to enable json output of "badmin lsfproxyd status" command.

about 1 month ago in Spectrum LSF / Scheduling 1 Planned for future release

1 VOTE

lsfproxyd - Persistent blocking rules

LSFProxyd is a new solution to help scheduler handle queries effectively. This RFE is to enable persistent blocksing rules for heavy query hitters. Same has been discussed with John Welch in a separate discussion.

about 1 month ago in Spectrum LSF / Scheduling 1 Future consideration

1 VOTE

Telemetry for LSF scheduler performance

LSF struggles in large farms with many running pending jobs and thousands of users in fairshare tree. LSF's struggle with heavy query activity is well documented. It would be great if LSF can provide telemetry on its own performance and what speci...

about 2 months ago in Spectrum LSF / Scheduling 1 Functionality already exists

2 VOTE

lsf proxyd logging in log file

From the documentations, it seems LSF proxyd is currently showing its logs from perfmon view style of command and this RFE is to enable lsf proxyd logging same as other daemons are logging currently. e.g. mbatchd.log, mbschd.log.. similarly we sho...

2 months ago in Spectrum LSF / Scheduling 1 Functionality already exists

1 VOTE

weighted throttling in lsf proxyd

From the documentations it seems, LSF Proxyd does not differentiates between a service account vs an individual user account and can't have diff policies for diff user accounts. Our farms have a good mix of service accounts which launch thousands ...

2 months ago in Spectrum LSF / Scheduling 2 Functionality already exists

1 VOTE

Cleanup user details with bqueues -lr output if they don't have running/done jobs in system

Currently, we can find thousands of entries for all users even though they have ZERO STARTED jobs as listed in bqueues -lr output. For some of larger farms, these entries are close to 7M records and bqueues -lr takes long time to return the data. ...

2 months ago in Spectrum LSF / Scheduling 0 Under review

2 VOTE

Expand API (or bjobs -o option) to report memory reservation on a per-job basis

Determining per-job memory usage is valuable, but we also need to be able to see, on a per-job basis, how much memory job(s) have reserved at a point in time. Partly we need to be able to compare to the actual memory use to see if they're over-res...

2 months ago in Spectrum LSF / Scheduling 0 Under review

1 VOTE

Affinity support for windows compute servers

We have a mixed Linux/Windows cluster. Unfortunately the affinity string in the resource requirement is not supported on Windows. This leads to several problems: 1. jobs with affinity settings will not be dispatched to windows nodes 2. less perfor...

4 months ago in Spectrum LSF / Scheduling 1 Future consideration

3 VOTE

Add possibility to assign cores from the same CCX in AMD CPUs to make use of the same L3 cache.

With a specific 2-core workload we noticed significant performance improvements of about 50% in shorter runtime when both cores reside on the same L3 cache group (CCX) of an AMD EPYC CPU.Therefore it would be very beneficial to be able to have LSF...

4 months ago in Spectrum LSF / Scheduling 0 Future consideration

1 VOTE

Use all applicable NUMA Memory information on a machine to determine available Memory resources before dispatching a job to a machine

We were noticing that jobs were being terminated by LSF with the message: TERM_MEMLIMIT: job killed after reaching LSF memory usage limit.Exited with exit code 137. Yet, this was happening before the job had even consumed the amount of memory rese...

6 months ago in Spectrum LSF / Scheduling 0 Future consideration

Please enter your email address

FILTER BY CATEGORY