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


Status Planned for future release
Workspace Spectrum Symphony
Components Version 7.2.0.2
Created by Guest
Created on Jan 15, 2020

Remove "obvious" deficiency in SSM scheduling when there are more than 10K open session #

When the Open Session number exceeds IBM's baseline of 10K, we can see Symphony SSM scheduling has an obvious "deficiency": Running task # starts to become much lower than the allocated slots to SSM bouncing between even 0 and very low; SSM busy on 1 thread (100%, while other threads pretty much idle). It is as if SSM were totally on haul. Note the total slots SSM can use is normally smaller the Open Session # often much smaller. The scheduling policy here is Proportional, although Priority policy also has this but likely less severe.

While we understand the 10K baseline, this deficiency is too obvious: Our sessions tend to be all at the highest possible say 10000. For a given # of allocated slots, SSM can only schedule certain # of highest priority sessions and any new or existing sessions do not need to be examined or re-examined for SSM dispatch scheduling E.g., if there's only 1 slot and it's used by a highest priority session, SSM doesn't need to do dispatch scheduling unil that 1 slot is freed. Sure this is not to say no scheduling related work such as preparation (like some sorting) needs to be done in the meantime but SSM doesn't need to be crazily busy as we observe about the scheduling thread

This looks like a relatively simple bottleneck to resolve instead of deep or fundamental change to SSM.

We can focus on proportional scheduling but good to see if similar bottleneck in priority scheduling.

Note it is very difficult to control the total open session # for our users/clients.