Aguasto Research · Revision 1Editorial record: Review and correction policy ↗
What was counted, and what useful work was delivered?
A hardware specification, an electricity ratio and a model-service price answer different questions. Facility overhead is not a measure of model quality. An announced development scope is not commissioned IT load. A unit-cost calculation needs a cost boundary, a time period and a denominator that treats failures, retries and output quality consistently.
Keep input assumptions separate from measured observations and from commercial commitments. Report utilization, acceptance, costs and token counts at compatible boundaries. Public operators’ disclosures can inform a case analysis, but they do not independently establish Aguasto costs, operating results, customers or financing outcomes.
Follow the evidence.
Expose the calculation
The tools show their formulas and bounds. Weight memory is a theoretical payload estimate; electricity scenarios omit costs outside their stated scope. Cost per million completed tokens divides a declared cost by a declared output count, and must not be mistaken for Aguasto token pricing.
Engineering tools ↗
Inspect hypothetical inputs, formulas and exclusions.Calculation policy ↗
Units, sensitivity and reproducibility.Keep efficiency and service outcomes separate
Power usage effectiveness compares facility energy with IT energy under a stated boundary. It does not establish how many useful model responses the IT equipment produced. Compare task quality, workload, location, reporting period and completed-request behavior before making an economic or environmental inference.
PUE, WUE and useful compute ↗
Separate infrastructure ratios from task-level output.Dedicated and shared inference ↗
Inspect operating assumptions rather than a price promise.Read reported milestones as evidence
Track the operator, date, unit and status attached to each disclosure. Announced, financed, contracted, ready-for-service and operating scope can overlap. Do not add rows without a common boundary or treat a corporate release as independent commissioning evidence.
Industry case analyses ↗
Dated third-party disclosures and explicit unknowns.Evidence classes ↗
Distinguish attributed claims, analysis and scenarios.
Cornerstone resources
Dedicated compute and shared inference: compare the whole workload
Provide a defensible cost-comparison method that includes idle reservation, completed tokens, operating scope and latency rather than a universal break-even claim.
Measuring PUE, WUE and AI Compute Efficiency at the Right Boundary
Build a measurement framework that connects facility overhead and water intensity to useful compute, without confusing device telemetry, ratios or hypothetical arithmetic with operating results.
Core Scientific: reading contracted, energized and billed capacity
Analyze dated public infrastructure disclosures with strict measurement/status distinctions; this is an independent third-party case, not an Aguasto customer story.
Keep these boundaries close.
Sources & verification
The register preserves each source's publication and verification date. Manufacturer claims and documentation are attributed; Aguasto has not run the cited products in production.
- Dedicated Model Inference — Together AI ↗
Provider distinguishes per-token shared service and GPU-hour dedicated resource billing; Dedicated and serverless are provider-specific service categories. Publication: date not stated in the reviewed source. Verified: 2026-10-12.
- Dedicated vs Serverless models — Together AI Knowledge Base ↗
Dedicated hardware has cost while idle; High utilization changes economic comparison. Publication: date not stated in the reviewed source. Verified: 2026-10-12.
- Autoscaling — Baseten official documentation ↗
Independent replicas; minimum/maximum capacity; Scale-to-zero and startup billing/cold-start latency; Running-replica billing boundary is provider-specific. Publication: date not stated in the reviewed source. Verified: 2026-10-12.
- Best Practices Guide for Energy-Efficient Data Center Design — DOE FEMP, July 2024 ↗
PUE measures supporting infrastructure rather than IT productivity; Annual PUE and site/source WUE distinctions; Heat-reuse host and backup heat rejection. Publication: 2024-07-26. Verified: 2026-10-13.
- Quantifying the impact on PUE and energy consumption when introducing liquid cooling — Vertiv/NVIDIA study summary ↗
Cooling changes can affect both sides of the PUE ratio; Vendor-modeled configurations are not universal measured savings. Publication: 2023-02-15. Verified: 2026-10-13.
- Recommendations for Measuring and Reporting Overall Data Center Efficiency, version 2 — DOE-hosted industry task force ↗
Dedicated and mixed-use measurement boundaries; Metering categories and disclosed assumptions; Comparisons need climate and reliability context. Publication: 2011-05-17. Verified: 2026-10-13.
- HPC Data Center Power Usage Effectiveness — National Laboratory of the Rockies ↗
Example of metered support loads and attributed shared loads; Site-specific ESIF reporting; not an Aguasto benchmark. Publication: date not stated in the reviewed source. Verified: 2026-10-13.
- Cooling Water Efficiency Opportunities for Federal Data Centers — DOE FEMP ↗
Closed equipment loop can reject to an evaporative tower; Annual site WUE definition; Treatment can add electricity and maintenance. Publication: 2019-01-09. Verified: 2026-10-13.
- Device Queries: Total Energy Consumption and Power Usage — NVIDIA NVML API Reference ↗
GPU energy counter in millijoules since driver reload; Power sampling behavior and unsupported-feature errors; Device telemetry does not meter all facility loads. Publication: date not stated in the reviewed source. Verified: 2026-10-13.
- Data Center Metering and Resource Guide — DOE Better Buildings ↗
Metering enables efficiency diagnosis and verification; Separate planning guidance from dated market statistics. Publication: 2016-07-28. Verified: 2026-10-13.
- United States Data Center Energy Usage Report: 2025 Update — LBNL, published June 2026 ↗
2030 reference case and sensitivity scenarios; Idle draw, utilization and lifetime assumptions; Consumption forecasts do not establish available grid capacity. Publication: 2026-06-18. Verified: 2026-10-13.
- Core Scientific Form 8-K Exhibit 99.2 — project disclosure ↗
Approximately 590 MW contracted net critical IT versus 900 MW secured grid capacity; Approximately 350 MW energized and over 185 MW billed as of March 13 2026; Phased delivery and completion expectations are forward-looking. Publication: 2026-04-21. Verified: 2026-10-12.
- Core Scientific Announces Second Quarter 2026 Results ↗
395 billing MW at Q2 end and 437 as of mid-July; Approximately 1.1 GW total leased customer power capacity includes expanded portfolio; Potential contracted revenue distinct from quarter revenue. Publication: 2026-07-28. Verified: 2026-10-12.