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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
[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.