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 Delivered
Workspace Spectrum LSF
Components Scheduling
Created by Guest
Created on Feb 19, 2024

THREAD limit to be set per HOST or PER CORE instead of PER JOB

The current THREADS limit on a queue level is set per job while it has to be set per HOST or per CORE.

That is because current limit doesn't reflect the size of a job so is the THREADS limit is 600 it means that a single core job can produce up-to 600 concurent threads which is A LOT and may lead to server hang and crash.

On the other side, if big MPI job was submitted on a 200 cores, than the 600 THREADS limit is too small for this size of a job and the job will crash.

By making the THREADS limit allocation per CORE or per HOST this will resolve the issue with the job sizes and each job will get the THREADS limit based on their size.

Needed By Month
  • Admin
    Bill McMillan
    May 20, 2024

    Hi Igor, great timing - as the patch has just been uploaded to fix central for this: 601992

  • Admin
    Bill McMillan
    Feb 26, 2024

    This is a reasonable requirement for a well defined use case.
    It has been moved the development backlog, and will addressed in due course.