Skip to Main Content
Cloud Management 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.

Status Future consideration
Workspace IBM Turbonomic ARM
Created by Guest
Created on Sep 15, 2025

Consistent sizing: Allow consistent number of vCPUs instead of consistent CPU capacity in MHz

Customers are not using MHz or GHz when they are dealing with CPU capacity of VMs but vCPUs. Thus, for a user consistent resizing shall - at least as an option - result in the same number of vCPUs.

For a user it’s really hard to understand if the different members of the consistent resizing group running on hosts with non-identical hardware/CPU types have divagating number of vCPUs, especially because this also has an effect on multi-threading.

Turbo compares CPU capacity using MHz and GHz, but from a user perspective Turbonomic needs to keep the number of vCPUs consistent even when the VMs are running on hosts with different HW/CPUs.

 

I will add screenshots with some examples.

Idea priority High