Skip to Main Content
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
Created by Guest
Created on Jul 15, 2020

Request to have app profile level settings to limit number of tasks executed in a persistent service instance

In a large cluster shared by 100's of applications from different LOBs, quite often, the a bad application workload might crash or disable servers by:
1) over consumption of system memory
2) filling up the root file systems with core files
3) etc
In the situation of over consumption of system memory case, even with the cgroup memory limit feature over symphony workload is set. We still see cases of system memory over consumption and crashes the server rapidly. The outcome of this is that a bad behaving application workload bring down servers along with the workloads from other applications (especially over long running tasks).
Per our observation, such bad application has the following characteristics:
1) The service instance persists to avoid the latency of starting the service instances
2) The run-time of its tasks is very short (in seconds if not in minutes)
3) If there is memory leak and/or slowness of freeing unused memory, it will resource a large accumulative memory foot print on the system.
4) The bad behavior will also leave no/less memory for other application workloads on the same server/system.
In order to avoid a bad application going wild, a new demand arise to have ability at the application configuration level to stop abusing the server by limiting the maximum number of tasks executed in a persistent service instance. So that, the application could release the memory faster and have the shared server more reliable to other good applications.

  • Guest
    Nov 29, 2020

    .Solution and sample code has been provided by Ajith to Andrew.

  • Guest
    Nov 26, 2020

    Solution and sample code has been provided by Ajith to Andrew.