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 46

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...
over 1 year 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...
over 1 year ago in Spectrum LSF / Scheduling 0 Planned for future release

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...
almost 2 years 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...
almost 2 years ago in Spectrum LSF / Scheduling 1 Not under consideration

Add support to Kerberos ticket with new "renew-until" date for already submitted jobs

While using Kerberos ticket forwarding on a LSF cluster: Currently TGT found on the submission host is copied to LSF cache and forwarded to the execution host at job submission; These tickets can be renewed automatically by LSF until the TGT "rene...
almost 4 years ago in Spectrum LSF / Scheduling 4 Not under consideration

Job slot of suspended jobs should be used in pending jobs

Hi Team, I would like pending jobs to be executed on the slots, where jobs are suspended using bstop command. Currently its not happening and those suspended job slots are remains unused. I request you to have a look and fix this issues in future ...
about 4 years ago in Spectrum LSF / Scheduling 1 Future 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...
about 2 years 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 2 years 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 2 years ago in Spectrum LSF / Scheduling 1 Not under consideration

Preemption support for MIG GPU jobs

We would like that preemption will be supported also for MIG jobs(A100 dgx mig devices). Currently the preemption is not working for this type of jobs. Example scenatiois: kill two or more jobs and reconfigure mig to have the new job run. We need ...
over 2 years ago in Spectrum LSF / Scheduling 2 Future consideration