Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Needs more information
Workspace IBM Turbonomic ARM
Created by Guest
Created on May 13, 2024

Size work loads for performance test only

Provide recommendations on cpu request and memory request based on performance test schedule .  

Scenarios : 

1. Spikey type of transactions like sending event notifications via email to other apps/customers. This demands for higher cpu/mem resources from containers to support spike data, but resources are idle rest of the time. This causes unnecessary hold of container resources.

In a QA/Test/PreProd environment we have long periods of time when testing is not happening and workloads are idle.  When the workloads do need to be used for testing they have been sized down and often times cannot start.  We need to be able to size these workloads based on specified time periods of use (performance test/regression test/load test) and only make recommendations around that timeframe, and not the timeframe when they were sitting idle and not being used. 




Idea priority High
  • Admin
    Jason Shaw
    May 13, 2024

    Thanks Sudarshana for taking the time to submit this Idea. An initial clarifying question on the ask, for such workloads could you not just remove the limits as to not limit the amount of vCPU/vMEM it can use, essentially letting it use the resources it needs when it needs it?

    Assuming you need to define a limit:

    To clarify the ask a little more you want to be able to schedule sizing up of a containerized workload on a certain day and time no matter what the resource utilization is.

    A a few questions on the ask:

    • Size up vCPU/vMEM limits or requests or both?

    • If both how would you like those defined (the same value or maybe the limits to be X% higher than requests for example)?

    Please let me know if you would like to discuss further via email or on a call,