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 Planned for future release
Workspace IBM Turbonomic ARM
Created by Guest
Created on Jul 7, 2023

CPU pinning workloads

As a user, I’d like to express a tolerance for CPU and memory for whole-core increments, like what we did for throttling. I'd like to set equal CPU request and limit (for OCR).


PM update to requirement:

We will implement support for rightsizing CPU Pinned workloads in 2 parts:

  1. introduce a setting that a user will specify locking limits and requests to resize together - a must to maintain the requirements for pinning workloads to a CPU

  2. introduce a setting where the user can express a toleration for CPU usage. Here the goal will be to allow pinned workload to have a targeted utilization of 50% or 25% which will influence the resizing to recognize scenarios where 1 out 2 or 1 out of 4 cores are in use.

Today the user can choose to set whole core increments for rightsizing but needs these other 2 features to ensure best actions for workload that is pinned to a CPU.

Idea priority Medium
  • Admin
    Eva Tuczai
    Reply
    |
    Aug 8, 2023

    We will implement support for rightsizing CPU Pinned workloads in 2 parts:

    1. introduce a setting that a user will specify locking limits and requests to resize together - a must to maintain the requirements for pinning workloads to a CPU (Epic TURBO-621)

    2. introduce a setting where the user can express a toleration for CPU usage. Here the goal will be to allow pinned workload to have a targeted utilization of 50% or 25% which will influence the resizing to recognize scenarios where 1 out 2 or 1 out of 4 cores are in use. (Epic TURBO-1745)

    Today the user can choose to set whole core increments for rightsizing but needs these other 2 features to ensure best actions for workload that is pinned to a CPU.