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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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

Status Under review
Workspace Spectrum LSF
Components Scheduling
Created by Guest
Created on Mar 31, 2024

Multiple queues request for job - consider taking in account queue limitations and lsf.resources for better job dispatching.

Today, when we submit a job with multiple queues (bsub "high risk") The job will be dispatched to a relevant queue by examine parameters such as queue status(open/closed), queue hosts, time-limit.

In a situation, where a queue "high" have a ujob_limit(1 for example) or ngpus number(1 for example) in lsb.resource - all the jobs still be submitted to the "high" queue instead of submitting just one job to high and others to risk. This makes the usage of multiple queues almost irrelevant and it does not improve the scheduling.

LSF should submit a job to a relevant queue based on: "On which queue job X will start to run faster. If on queue high I have reached the ujob_limit or ngpus limit --> submit the next job to risk queue".

Needed By Month