IBM Software / SaaS Global

IBM

IT Operations Automation

IBM Research's Big AI Models team needed to keep scarce GPUs available for a growing set of LLM experiments and inference workloads, but overprovisioned Kubernetes instances were wasting expensive accelerator capacity and forcing engineers to spend time manually monitoring and resizing resources.

13 fewer GPUs will be necessary in a full automation environment
2x throughput achieved without degrading the latency performance
5.3x increase in idle GPU resources
running over 100 NVIDIA A100 GPUs

Reported impact

Business outcome

IBM increased idle GPU availability from three to sixteen, doubled throughput without hurting latency, and projected that full automation would eliminate the need for thirteen GPUs, while also freeing engineers from constant manual performance monitoring.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

IBM's Big AI Models team deployed IBM Turbonomic to automate resource management for its internal generative-AI environment. The BAM platform supports engineering teams testing and refining LLM projects on Kubernetes-based inference services backed by more than 100 NVIDIA A100 GPUs. Turbonomic continuously evaluates real-time utilization data, recommends optimal actions, and can automatically scale instances up or down so workloads get the right amount of GPU-backed capacity without overprovisioning. That let the team convert manual monitoring into policy-driven optimization, free idle GPUs for other users, and time-share infrastructure instead of reserving dedicated capacity. The resulting setup preserved performance while increasing throughput and cutting the number of GPUs required in a fully automated environment, turning hybrid-cloud optimization software into a practical control plane for high-demand AI infrastructure.

Data flow

Runtime utilization telemetry from BAM's Kubernetes-hosted LLM services is analyzed by Turbonomic, which recommends or triggers scaling changes so GPU capacity is released from overprovisioned instances and reassigned to other active workloads.

Solution architecture

3 components · 2 layers
  1. Compute
    • NVIDIA A100 GPUs Provide the accelerated compute pool that BAM shares across model testing and inference workloads.
  2. Orchestration
    • IBM Turbonomic Analyzes runtime demand and automates scaling decisions to optimize BAM's GPU-backed LLM services.
    • Kubernetes Runs the LLM inference instances that are scaled up and down based on Turbonomic recommendations.

Architecture clues

  • The BAM environment runs LLM services on Kubernetes and shares a pool of NVIDIA A100 GPUs.
  • The team adopted time-sharing to reuse GPUs across multiple workloads.
  • Turbonomic uses real-time data and can execute automated scaling actions.

Evidence from the source

Now, with scaling and sharing, IBM BAM team showed 13 fewer GPUs will be necessary in a full automation environment.
To optimize their GPU resources and manage their LLM Kubernetes instances, the IBM BAM team deployed IBM Turbonomic
With Turbonomic, the IBM BAM team was able to create a scalable and agile infrastructure
the team show the ability to increase the idle GPU resources from 3 to 16 (5.3 times)
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    IBM customer story

    First-party
    https://www.ibm.com/case-studies/ibm-bam-turbonomic
    Source type
    Vendor-published customer story
    Published
    Aug 6, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.