NVIDIA Software / SaaS United States

Lambda

Lambda needed to raise token throughput and improve AI-cloud economics, but fixed rack and facility power budgets were leaving GPU capacity stranded and limiting how many nodes could run safely at once.

+17% Hybrid Training Throughput
+20% Hybrid Inference Throughput
+23% Performance per Watt
+24% Cluster-Wide Token Throughput

Reported impact

Business outcome

Lambda increased cluster-wide token throughput by 24 percent, improved performance per watt by 23 percent, raised hybrid inference throughput by 20 percent, and lifted hybrid training throughput by 17 percent without expanding the facility power budget.

  • Cost Reduction
  • Productivity Improvement
  • Scalability

Solution

Lambda validated NVIDIA's DSX AI Factory Platform as an operational layer for power-constrained AI clusters rather than just a benchmark feature. On a five-rack HGX B200 environment, DSX MaxLPS and its Dynamic Power Software monitored GPU and rack-level draw in real time, then redistributed available power so more nodes could run under the same facility ceiling. Operators set policy targets such as 80 or 85 percent of maximum node draw without modifying active workloads, which allowed Lambda to pack additional inference and training nodes into the same footprint while keeping visibility through power-observability dashboards. Because mixed inference and training jobs have different power curves, the system could reclaim capacity that static provisioning leaves idle. That architecture turns power shaping into a control plane for AI-factory utilization, not just a hardware setting, and gives Lambda a path to lower cost per token as clusters scale.

Data flow

Training and inference workloads are scheduled onto HGX B200 nodes, where Dynamic Power Software tracks live consumption and DSX MaxLPS applies per-policy power targets. The adjusted node budgets let Lambda run additional servers, and throughput and observability metrics feed back into cluster operations for ongoing tuning.

Solution architecture

4 components · 4 layers
  1. Compute
    • NVIDIA HGX B200 GPU servers Host the training and inference workloads whose power envelopes are optimized by the DSX stack.
  2. Serving
    • NVIDIA DSX MaxLPS Applies policy-based power shaping so Lambda can run more cluster nodes within a fixed budget.
  3. Orchestration
    • NVIDIA DSX AI Factory Platform Provides the broader design, simulation, and operations framework Lambda uses to improve AI-factory efficiency.
  4. Governance
    • Dynamic Power Software Monitors rack and GPU power draw in real time and reallocates capacity to maximize throughput.

Architecture clues

  • Lambda tested DSX MaxLPS across a five-rack, 19-node cluster of HGX B200 systems
  • Mixed training and inference workloads are used to reclaim stranded power headroom
  • Policies were evaluated at 80% and 85% of maximum per-node draw
  • The platform uses rack-level observability dashboards refined through Lambda's feedback

Evidence from the source

Dynamic Power Software (DPS) monitors GPU and rack-level consumption in real time, reallocating power to where it is needed to maximize token throughput within fixed budgets.
NVIDIA DSX MaxLPS enabled Lambda to add two inference nodes within the same power budget, increasing throughput by 20% in concurrent inference and training configurations.
NVIDIA DSX MaxLPS increased cluster-wide throughput per watt by 23% while operating within the same fixed power budget.
Using NVIDIA DSX MaxLPS, Lambda ran 19 nodes instead of 16 within the same power budget, increasing cluster-wide token throughput by 24% and GPU capacity by 19%.
Transparency Evidence & methodology 100/100 reference value · 92% confidence · 2 sources

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
    4 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 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 transparency9/10
    2 source references 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. NVIDIA

    Lambda customer story

    First-party
    https://www.nvidia.com/en-us/case-studies/lambda/
    Source type
    Vendor-published customer story
    Published
    Sep 15, 2026
    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
  2. Built In

    Lambda Careers, Perks + Culture | Built In

    Independent secondary
    https://builtin.com/company/lambda

    The Organization JSON-LD lists addressLocality "San Francisco", addressCountry "US", and numberOfEmployees value 106.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • Published on source page Sep 15, 2026 · NVIDIA · First-party
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.