Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Add a new idea Subscribe
Status Submitted
Workspace IBM Turbonomic ARM
Categories Container Platforms (K8s & OpenShift)
Created by Guest
Created on Jul 6, 2026

RELATED IDEAS

Turbonomic CPU Throttling Prevention - Container Spec

Issue: After Turbonomic reduces vCPU limits based on utilization, CPU throttling occurs (80-90%), requiring the limit to be increased again 1-2 days later, potentially causing performance degradation across services and requiring Atruvia OCP team to scale back up resources that have only just been scaled down, multiple changes of the same container!

Turbonomic resource optimisation relies primarily on utilisation metrics over a defined period, i.e. 30 days, without consideration for CPU throttling metrics.

  • CPU utilization may be low (e.g., 30-40% of limit)

  • But CPU throttling can still be high (80-90%)

  • This occurs when workloads have bursty CPU patterns

Atruvia's policies require all resizing changes to be manually executed.

Every Turbonomic resize action will require the Atruvia service owner to manually create a change request and to go through an approval process, so automating vCPU scale up actions is not possible.

Risk Limitation: Rate of Resize seperate for all Resources, especially for vCPU Limit

We discussed a potential IDEA and work around of being able to adjust the Rate of Resize for vCPU Limit only in policy settings that controls how aggressively Turbonomic applies a calculated vCPU resize recommendation.

Low (1)

Changes the vCPU allocation by one resize increment only. For VMs, this is typically one vCPU (or one configured MHz increment, depending on the scaling policy).

Medium (2)

Moves the VM 25% of the way from the current allocation to the calculated optimal allocation.

High (3)

Resizes the VM directly to the optimal vCPU allocation in a single action. This is the recommended default in current IBM Turbonomic versions.


It would also be beneficial if you could configure an increment/decrement value for the rate of resize, that you dont have to choose between 1,2 or 3 but also can configure the decrement step, i.e 100mCores or 300 mCores. That would help to be more aggressive in pre-prod stages and more conservative in Production instead of only having the option of low, medium and high.

Idea priority High
  • Guest
    Aug 6, 2026

    Spoke with the Atruvia team and explained the situation that ideally we would like them to look at implementing all the suggestions Pankaj made in regard too:  CPU throttling tolerance, Aggressiveness, Min & Max observation period.  They have attempted this at a global scale, so for example, CPU throttling tolerance is now set globally.  I asked them whether there is a specific candidate we could work with, friendly business application owner who is seeing recommendations to scale down vcpu followed by seeing requests to scale up vcpu.  Atruvia advised that the next time a team highlights this, they will ask them to be a test candidate for the recommendations. 

    Reply
  • Guest
    Aug 6, 2026

    Before we can prioritize PM team want to ensure all the suggestions that were made on call by Pankaj have been exercised and has resolved/remediated the issue.

    Reply
  • Guest
    Jul 30, 2026

    We should also look into whether Requests and Limits could also be separated for bi directional sizing independently.

    Reply
  • Guest
    Jul 30, 2026

    Additional recommendations were for adjustments too: 

     

    CPU throttling tolerance A low percentage value indicates more sensitivity to throttling, change default 20% to 10%

    Aggressiveness, try increasing from default 99% up to 99.9% for more sensitive workloads

    Look at potentially adjusting Max observation period and Min observation period, a shorter period for more sensitive workloads means that there are fewer data points to account for when Turbonomic calculates usage percentiles. This shorter period results in more dynamic, elastic resizing, while a longer period results in more stable or less elastic resizing.

    Reply
  • Guest
    Jul 30, 2026

    After discussions with the customer and PM team, recommendation is for bi directional commodity based vcpu and vmem rate of resize values so that rate of resize can be configured independently for both vcpu and vmem.  This would enable customers to set optimal values independently, for example: vCPU set to -3 and vMem set to -1.

     

    Reply
  • Guest
    Jul 9, 2026

    aggressiveness scaling constraint is using default P99

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.