IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Spectrum Symphony
Components Version 5.1
Created by Guest
Created on May 22, 2015

[Resource Management Policy] EGO - Policy - Enforce limit set at parent consumer level under Hybrid model

It is confirmed in PMR 39339,7TD,000 that resource limit set at parent level in hybrid sharing model could be breached and this is not avoidable due to unpredictable workload pattern, e.g two sub-consumers are over-allocated but within parent limit, later a third consumer owning large number of slots will get slots allocated with its new demand. And under this case, limit set at parent level will be breached.
This is ok if it happens for a short interval. But if the over-slotted consumer sets a large grace period, say 24 hours or even longer, ego will wait until grace period expires to get back these slots. During this time, the parent limit is breached and some other consumers will starve even they own slots.
This is not fair and symphony should at least expose some parameters to allow changing this behavior.
One suggestion is to provide parameters to change this reclaim behavior, i.e. keep current default behavior of reclaiming over-allocated slots in (reclaim_timeout + 2 minutes), but allow user to set parameter, say EGO_HYBRID_ENFORCE_PARENT_LIMIT=true (can default to false), to flag that EGO should forcefully reclaim back these over-allocated slots in min(EGO_HYBRID_RECLAIM_TIME,reclaim_timeout)+2 minutes. As these are over-allocated slots rather than owned slots, EGO should be able to force reclaim back slots upon this flag set to true. Of course, these parameters should not affect reclaiming slots by ownership rather it should be for borrowed/over-allocated slots only.

  • Guest
    Dec 4, 2020

    Advanced sharing policy including consumer level exclusive and MDS have been added to Symphony since 7.2.x release.

  • Guest
    Mar 14, 2017

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.

  • Guest
    May 23, 2015

    Creating a new RFE based on Community RFE #71627 in product Platform Symphony.