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 of 14440

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

Why do we have to run "lspasswd" to register windows user's password in LSF ?

Customers hope they don't need to use lspasswd in Windows. But LSF needs user's password to impersonate user before running user's job on a Windows execution host. This is due to the designed feature of user authentication in Windows. Windows need...
almost 2 years ago in Spectrum LSF / Scheduling 1 Not under consideration

Improve Various Components of the Current Scheduler Adlgorithm

Currently, though the Scheduler supports threads, the processing is not a thread per bucket, but rather a threads that are used on a per bucket basis and buckets are still handled serially, which has led us to Host Match times around 400 seconds. ...
about 2 years ago in Spectrum LSF / Scheduling 4 Not under consideration

Have LSF track the number of status changes and requeues for a job over time

Basically, right now, there is no way to look at LSF's jobInfo record to know how many times a job has been requeued via either a pre-exec/jobstarter failure, or from a manual requeue. Additionally, there is no way to determine how many times a jo...
over 2 years ago in Spectrum LSF / Scheduling 1 Not under consideration

Customize date output format for bjobs, bacct, bhist commands

Current output for date format is Apr 17 03:06:23. Customer prefers this date format: 2022 04/17/2022 03:06:23
almost 2 years ago in Spectrum LSF / Scheduling 1 Not under consideration

Reduce the Scheduler impact of a "bmod -sp"

Currently, a bmod is a very expensive activity in LSF, but running a bmod to simply change a jobs priority, should be a low impact changes. What we would request is to have the bmod that simply does an '-sp' to be handled in a way that has the lea...
about 2 years ago in Spectrum LSF / Scheduling 0 Future consideration

Normalize and Remove SELECT "OR" clause in Effective Reservation Requirements

When a job that is pending for a -R "select[this || that]" should be normalized to either select[this] or select[that] upon dispatch so that the user can tell what set of requirements were used to dispatch the job, but this is not currently the be...
over 2 years ago in Spectrum LSF / Scheduling 1 Not under consideration