From the NVIDIA edition of September 19, 2026
DataCenterNews Sep 18: power-efficiency deals span Flex, MaxLPS, Annapurna, d-Matrix, Pinterest
DataCenterNews · Data-center trade press · Global (Santa Clara AI Infra Summit coverage)
- Publisher
- DataCenterNews
- Original publication
- September 18, 2026
- Source retrieved
- 2026-09-20
- Event date
- 2026-09-18
What happened
Sep 18, 2026 DataCenterNews recounts Ian Buck AI Infra Summit framing around tokens per megawatt and catalogs efficiency-related collaborations: Emerald AI + Silicon Valley Power flexible-load programme responding to hundreds of utility signals; Lambda MaxLPS PoC (+24% tokens/s, +23% perf/W, 19 vs 16 nodes); Amazon Annapurna Labs NVHBM custom HBM work; d-Matrix NVLink Fusion with Vera CPUs + Raptor XPUs; Pinterest Blackwell + Dynamo for conversational visual discovery; Vera Rubin + Groq 3 LPX claims up to 35x tokens/MW vs GB200 on long-context; AgentX up to 30x tok/MW and 45x lower cost per million tokens vs GB300 on DeepSeek V4 Pro; NVLink 6 reliability features for large factories.
Why it matters
Same-day complementary reporting to yesterday Flex/MaxLPS piece with additional ecosystem partners (Annapurna, d-Matrix, Pinterest, Groq). Useful as a map of claims for SLED scanners; still vendor-sourced metrics via trade press. Limited direct agency deployment evidence.
Evidence and measured results
Flexible-load hundreds of signals; Lambda 19/16 nodes 4 to 5M tokens/s; Annapurna NVHBM; d-Matrix NVLink Fusion; Pinterest Dynamo; Groq 3 LPX 2529 tok/s/user on 100K-context Qwen example; AgentX 30x/45x claims; NVLink 6 fault isolation narrative.
Limitations and uncertainty
Trade press based on NVIDIA/partner statements; methodologies differ; overlaps prior MaxLPS/Flex coverage.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-20; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Buyers hear many efficiency announcements and need triage.
- Stakeholders
- CIO
- facilities
- AI platform
- Discovery questions
- Is your blocker interconnect, rack power, or serving latency?
- Which partner lane matters now?
- What evidence standard will you accept?
- Value hypothesis
- Selecting one efficiency lane with matched proof beats bundling every Summit claim.
- Potential engagement
- Efficiency-lane triage workshop tied to one pilot.
- Unsupported claims
- All multipliers stack multiplicatively
- Annapurna/d-Matrix ready for every SLED site
- 35x/30x portable defaults
Pre-sales engineering
Role takeaway
- Fit
- Horizon planning for AI factory programs.
- Architecture and integration
- Separate Flex, MaxLPS, Dynamo, and accelerator-fusion tracks.
- Prerequisites
- clear bottleneck diagnosis
- metering
- serving baseline
- Constraints
- Vendor-reported metrics
- early partner tech
- overlap with prior coverage
- Security
- Assess each lane control plane separately.
- Proof of value
- One-lane pilot metrics
- No double-counted multipliers
- Rollback per lane
Delivery
Role takeaway
- Work
- Charter lane owners and evidence standards; reject stack-ranked mega-claims.
- Dependencies
- facilities
- platform
- partner SEs
- Ownership
- AI infrastructure PMO.
- Skills and adoption
- PMs must distinguish Flex vs MaxLPS vs serving efficiency.
- Governance checkpoints
- Lane charter approved
- Evidence standard set
- Summit slides not used as acceptance
- Acceptance criteria
- Pilot chosen
- Metrics defined
- Non-goals listed
- Risks
- Scope sprawl
- Metric stacking
- Partner vapor
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Efficiency roadmap spans grid Flex, MaxLPS densification, custom memory, CPU+XPU fusion, and Dynamo multimodal—evaluate as separate workstreams.
Governance
Who approves, reviews and stays accountable for outcomes?
Keep partner announcements from collapsing into a single NVIDIA solves power budget assumption.
Security and privacy
What data, permissions and controls need testing?
Not primary focus.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None stated.
Procurement
What should contracts, pricing and exit terms secure?
Split RFPs by efficiency lane; forbid multiplicative stacking of unrelated multipliers.
Operating model
Which teams own the service once it runs?
Tokens/MW becomes the shared vocabulary across facilities and platform teams.
Publication history
- 2026-09-19NVIDIA · Issue 148 resources
Stable resource ID: datacenter-news-power-efficiency-deals-20260918