Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


ADD A NEW IDEA

Scheduling

Showing 37

Correct on Design Flaw in Session Scheduler

Currently the Session Manager and Service Director operate in the same CGROUP on the first execution host which causes a race condition that if a task on the first execution host pushes the memory use above the memory limit (aka mem-eater process)...
5 months ago in Spectrum LSF / Scheduling 1 Not under consideration

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.
7 months ago in Spectrum LSF / Scheduling 1 Future consideration

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. ...
8 months ago in Spectrum LSF / Scheduling 2 Planned for future release

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...
10 months ago in Spectrum LSF / Scheduling 1 Future consideration

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...
12 months ago in Spectrum LSF / Scheduling 0 Future consideration

LSF to track SSH and child processes on machines running LSF jobs

To prevent users from sshing into nodes that they do not have a running job on, to restrict the SSH session to the resources that the runing job has on the machine (e.g. cgroups ), to track the ssh connection and any other spawned processes for ac...
12 months ago in Spectrum LSF / Scheduling 0 Future consideration

Allow preemption of shared gpu jobs (j_exclusive=no) by higher priority job queues.

We need the LSF support for preemption of shared gpu jobs. Currently GPU preemption is supported only for jobs in mode j_exclusive=yes This is a very big problem as we have a significant waste of gpu memory resource. because if a lower priority jo...
about 1 year ago in Spectrum LSF / Scheduling 1 Not under consideration

Dynamic priority based on jobarray length

We exclusively work with jobarrays at our company. We have a queue reserved for jobs that take no more than 3 minutes. A general rule of thumb is that small jobarrays at our company can be considered as interactive jobs where the user waits for th...
over 1 year ago in Spectrum LSF / Scheduling 0 Not under consideration

LSF does not allow jobs to moved from low to high/medium priority queues if there are limits set on medium/high priority queues

We have a setup as follows 1) High queue limit 3 2) Medium Queue limit 4 3) Low queue no limit and the default queue for usrs to submit jobs 4) Very low queue, will be used to use licenses effectively When a user submits 6 jobs for example in high...
over 1 year ago in Spectrum LSF / Scheduling 1 Future consideration

allow update for span string after a job is started

Hello, currently, it's not possible to update the span string after a job is started. for ex: a user start a multinodes jobs using bsub .... -n x -R ".. span[ptile=y]" ... unfortunately, he forgot to specify to the tool to start in mutlinodes an...
over 1 year ago in Spectrum LSF / Scheduling 1 Not under consideration