Scheduling

Showing 10

Affinity scheduling must take L3 cache hierarchy into account

Newer CPUs have multiple L3 caches, with dedicated cores per L3 cache. Running multi-threaded jobs on all cores within a shared L3 cache can reduce runtime in our cases up 70%, compared to running over multiple L3 caches. Think of the AMD EPYC 935...

about 2 months ago in Spectrum LSF / Scheduling 2 Planned for future release

1 VOTE

Improve bsub rejection messages for troubleshooting

Improve the error messages returned from bsub failiure. For example, provide the rusage string and potentially specified what is wrong with rusage. Here is current failure message: Error in rusage section. Job not submitted.

2 months ago in Spectrum LSF / Scheduling 0 Planned for future release

1 VOTE

LSF job query filter on pending jobs without providing pending reasons

For large LSF clusters, the bjobs command takes significant time to gather the pending reasons (-p, -pei, -pe, -pi) making the query much longer than requesting all jobs. Suggest a new bjobs option to filter on pending jobs without supplying the p...

3 months ago in Spectrum LSF / Scheduling 0 Planned for future release

4 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...

over 1 year ago in Spectrum LSF / Scheduling 0 Planned for future release

2 VOTE

Enhance lsmake4 to support Grouped Target's in the latest version of make 4.4.1

Currently our tools are using Grouped Target's which don't properly work causing quite a bit of rework after the initial compile.

10 months ago in Spectrum LSF / Scheduling 0 Planned for future release

1 VOTE

truncated hostnames in bjobs output

For a debug where hosts are available but jobs are not landing on them - I need to run bjobs -UF (or -l) -p2 This command generates below like data structure Slots are reserved for guarantees: xxx3-sim-d18-081, xxx-sim-d18-077, xxx- sim-d30-065, x...

6 months ago in Spectrum LSF / Scheduling 0 Planned for future release

2 VOTE

tool to list out active and default base params - lsparams

Think of 'bparams' and the level of details that it provides with args '-la'. This helps in figuring out what all params are configured as default or what defaults values are affecting the scheduling. Such a tool does not exist for LSF Base config...

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

1 VOTE

INCLUDE directive for lsf.cluster file

Its great to have INCLUDE functionality added in LSF and we're using heavily in our multiple LSF clusters. Its makes it easy to manage many clusters for common config edits and keep the farms compliant. I am logging this RFE to extend this feature...

7 months ago in Spectrum LSF / Scheduling 1 Planned for future release

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. ...

over 1 year ago in Spectrum LSF / Scheduling 2 Planned for future release

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...

over 1 year ago in Spectrum LSF / Scheduling 0 Planned for future release

Please enter your email address

FILTER BY CATEGORY