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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
[Process]ToSlotRatio implementation across soam and ego
In symphony SOAM layer, in application profile, service instance has serviceToSlotRatio defined which tells the system how much cluster compute resources each symphony task would take upon execution. * Funny enough, there is no such serviceToSlotRatio defined for session manager. Whatif any application requires more intensive processing in session manager (hence more memory or cpu power required). Would symphony allow an SSM instance to book more system resources on the SSM host? Besides, a multi-threaded SSM does require more cpu and memory sometimes, it is a fundamental component for any application. * Even funnier, there is no such serviceToSlotRatio/instanceToSlotRatio allowed in EGO layer when ego service instances might need more system resources to perform regularly...
It is a bad design that a [proc]ToSlotRatio concept does not cover all area in a system...
Do not place IBM confidential, company confidential, or personal information into any field.