Track 1
AI Compute 101
Start here. GPUs, GPU-hours, model costs, and why compute became a market.
0 of 7 complete
Free lessons, calculators, and explainers for understanding GPUs, model costs, prompt and context design, cloud capacity, data centers, power constraints, and emerging AI compute infrastructure. Explore 81 published lessons, follow a learning path, or use a calculator to estimate real compute costs.
A different lesson is highlighted in the Morning Brief each day.
Sponsor slot available
Reserved placement for infrastructure, data-center, energy, and AI compute sponsors.
View sponsor optionsThe curriculum
Pick a track and work through it in order, or jump to the topic you need. Track your progress in this browser — no account required. Every lesson is free.
Track 1
Start here. GPUs, GPU-hours, model costs, and why compute became a market.
0 of 7 complete
Track 2
What H100, H200, and B200 hours cost, and how on-demand, reserved, and spot pricing differ.
0 of 8 complete
Track 3
What it costs to train a model and to serve one, and why utilization drives the bill.
0 of 7 complete
Track 4
How prompts, context, retrieval, and agent state shape model quality, token usage, latency, and inference cost.
0 of 2 complete
Track 5
How benchmark scores connect to token pricing, latency, throughput, and real inference spend.
0 of 23 complete
Track 6
Power, cooling, networking, memory, and the physical sites where AI compute actually runs.
0 of 17 complete
Track 7
Neoclouds, capacity markets, and reservations: how compute supply gets priced.
0 of 8 complete
Track 8
Forward pricing for compute: futures, forward curves, and forward contracts.
0 of 5 complete
Track 9
How labs and teams buy, compare, and budget GPU capacity in practice.
0 of 8 complete
Compute College tracks
Once you know the basics, work through pricing, model costs, prompt and context design, infrastructure and power, market structure, compute futures, and the buyer-and-operator playbook. Emerging topics and the calculators sit alongside them.
AI compute is the hardware, power, networking, and cloud access used to train and run AI models.
AI capability becomes a market constraint when usable compute is scarce, costly, or slow to deliver.
The core unit for calculating AI GPU rental cost, utilization, and workload budgets.
How NVIDIA accelerator generations compare on workload fit, current GPU-hour pricing, memory, and availability.
Model training cost is the compute expense required to teach or improve an AI model from data.
Frontier model serving cost is the estimated expense of running a leading AI model for users after training.
Why electricity, interconnection, and site readiness now constrain GPU deployment.
H100 price per hour is the hourly cost of accessing one NVIDIA H100 GPU for an AI workload.
H200 price per hour is the hourly cost of accessing one NVIDIA H200 GPU for AI workloads.
B200 price per hour is the hourly cost of accessing NVIDIA B200-generation AI compute capacity.
GPUs, TPUs, and custom ASICs are different kinds of AI accelerator that trade flexibility for efficiency on targeted workloads.
On-demand, reserved, and spot GPU pricing are three ways buyers obtain and pay for AI compute capacity.
How rented accelerator capacity turns GPU access into observable market pricing.
How interruptible GPU capacity prices expose marginal AI compute supply.
GPU cloud capacity is buyer-accessible accelerator supply available for AI workloads through cloud providers.
Model training cost is the compute expense required to teach or improve an AI model from data.
Frontier model serving cost is the estimated expense of running a leading AI model for users after training.
Cost per million tokens is how hosted AI APIs price inference — usually with input and output tokens priced separately.
GPU utilization measures how much paid accelerator capacity is actively doing useful work.
Model FLOPs Utilization (MFU) measures how much of a GPU's theoretical compute a job actually uses; goodput counts useful work delivered.
GPU depreciation spreads an accelerator's purchase cost over its useful life, which drives the real cost of every GPU-hour.
Monthly AI compute burn measures recurring spending on the capacity used to train, fine-tune, experiment, and serve models.
How clear instructions, examples, constraints, and output formats help an AI model complete a task.
How AI systems select and manage the information a model receives before making a decision.
Learn what AI model benchmarks measure, where they mislead, and why benchmark results can become compute demand and cost signals.
AI model benchmarks compare models on fixed tasks, but their scores only become useful for AI compute buyers when read with cost, latency, and token use.
Learn why AI benchmark scores can mislead buyers when they hide prompt setup, retries, tool use, latency, token usage, and model serving cost.
Learn how to compare AI model benchmark performance with token pricing, latency, throughput, and cost per useful result.
Learn why higher AI benchmark scores may not lower production cost, and how token usage, latency, retries, and context size affect serving spend.
Learn how to estimate the full cost of an AI task, including input tokens, output tokens, retries, tool calls, latency, and model selection.
Learn what AI model latency means, why it matters for production workloads, and how it connects to model serving cost and infrastructure capacity.
Learn what tokens per second means, how model throughput affects AI applications, and why throughput matters for AI compute capacity planning.
Learn what an AI model context window is and how longer context affects token cost, memory, latency, and model serving economics.
Learn what AI coding benchmarks measure and why coding-agent benchmarks matter for inference demand, model serving cost, and AI compute capacity.
Learn what SWE-bench measures, why it matters for AI coding agents, and how software-engineering benchmarks connect to AI compute demand.
Learn what LiveCodeBench measures, why fresh coding tasks matter, and how contamination-resistant coding benchmarks affect AI model evaluation.
Learn what Terminal-Bench measures and why terminal-based AI agent benchmarks matter for token usage, latency, and AI compute demand.
Read Claude Opus 4.8 benchmark claims as AI compute economics evidence: capability-per-dollar, effort settings, fast mode, agent workloads, and serving demand.
Claude Mythos Preview is an unreleased Anthropic frontier model used in Project Glasswing for defensive cybersecurity work.
Learn what GPQA Diamond measures, why expert science reasoning benchmarks matter, and how they connect to frontier AI compute demand.
Learn what MMLU-Pro measures, how it differs from older academic benchmarks, and why benchmark difficulty matters for AI model evaluation.
Learn what Humanity’s Last Exam measures and why frontier academic benchmarks matter for model capability claims and AI compute demand.
Learn what AI reasoning benchmarks measure and how reasoning scores connect to model serving cost, latency, and frontier AI compute demand.
Learn what AI agent benchmarks measure and why agentic workflows can drive higher token usage, latency, retries, and AI compute demand.
Learn how new AI model releases can change inference demand, training demand, token usage, cloud GPU capacity, and the AI compute market.
Learn why output tokens usually cost more than input tokens and how generation cost affects model serving economics, AI agents, and inference spend.
Reasoning models generate long chains of thought before answering, multiplying output tokens — and output tokens drive inference cost.
Why electricity, interconnection, and site readiness now constrain GPU deployment.
The facility stack that turns accelerators into operating AI compute supply.
Cooling removes the heat created by dense AI hardware so a facility can deliver usable compute safely.
How interconnect quality turns GPU count into useful clustered compute.
How high-bandwidth memory affects model fit, GPU value, and accelerator availability.
An AI cluster is a connected system that turns many GPUs and supporting infrastructure into usable model-training or serving capacity.
NVLink is a high-speed GPU connection technology that helps accelerators coordinate work inside AI systems.
InfiniBand is high-performance networking used to connect servers in many large AI clusters.
NVL72-style rack systems link many GPUs into one; it illustrates scale-up (bigger tightly-coupled units) versus scale-out (more networked units).
Liquid cooling removes heat from dense AI hardware so more compute can operate reliably in a facility.
Data center interconnection links AI capacity to networks, clouds, data sources, and buyers who need to use it.
Power Usage Effectiveness measures how much facility electricity is required to deliver useful IT power.
AI data centers secure electricity through PPAs, behind-the-meter generation, and firm low-carbon sources like nuclear and SMRs.
A megawatt of AI compute is a power-based way to describe possible data-center and accelerator capacity.
A data center interconnection queue is the waiting line for large facilities seeking electrical grid connection.
AI data center cooling density describes the heat-removal capacity required by concentrated GPU racks.
High-bandwidth memory is fast memory located near advanced accelerators to keep AI workloads supplied with data.
How compute-first cloud operators sell GPU clusters, reservations, and AI capacity.
A compute capacity market organizes access to AI compute as priced, reserved, allocated, or future-delivered capacity.
GPU cloud capacity is buyer-accessible accelerator supply available for AI workloads through cloud providers.
A compute reservation secures defined GPU or accelerator capacity for a buyer over an agreed period.
How rented accelerator capacity turns GPU access into observable market pricing.
How interruptible GPU capacity prices expose marginal AI compute supply.
GPU-backed financing is borrowing against GPUs or their rental contracts to fund AI infrastructure without paying the full cost upfront.
Sovereign AI compute is AI capacity a country controls within its own borders and jurisdiction, reducing dependence on foreign infrastructure.
How forward prices turn future GPU capacity into a planning and market signal.
How curve shape signals expected tightness, relief, or uncertainty in future compute supply.
A compute forward contract agrees today on a price for defined compute capacity delivered at a future time.
A compute capacity market organizes access to AI compute as priced, reserved, allocated, or future-delivered capacity.
A compute reservation secures defined GPU or accelerator capacity for a buyer over an agreed period.
AI labs secure usable capacity through rentals, reservations, cloud agreements, owned clusters, and strategic infrastructure deals.
Comparing GPU cloud quotes means normalizing rate, capacity quality, access terms, and expected completed-workload cost.
Eleven concrete fields to compare on every GPU cloud quote before signing.
Monthly AI compute burn measures recurring spending on the capacity used to train, fine-tune, experiment, and serve models.
Spot GPUs suit flexible work; reserved capacity suits predictable or critical AI workloads that need dependable access.
A neocloud service level agreement defines reliability and remedy terms for specialist GPU-cloud capacity.
AI compute procurement is the disciplined process of sourcing and managing accelerator capacity for AI workloads.
GPU utilization measures how much paid accelerator capacity is actively doing useful work.
Estimate AI compute cost from GPU price, runtime, utilization, and overhead.
Estimate a training-run budget using GPU-hours and operating assumptions.
Estimate recurring inference cost from usage and capacity needs.
Compare committing to reserved GPU capacity against paying on-demand for a workload.
Compare paying per token for a hosted API against running the model on your own GPUs.
Read Claude Opus 4.7 benchmark claims as AI compute economics evidence: capability, token pricing, workload fit, and likely inference demand.
How multi-gigawatt AI campuses translate power plans into future compute supply.
Why a large GPU cluster is a compute-market signal only when powered, cooled, and usable.
How custom AI silicon can expand or redirect demand for GPU-equivalent compute.
How a mega-scale AI infrastructure buildout can affect future compute supply.
Why a proposed fab or capacity project matters only when milestones become deliverable supply.
Put it to work
Use the GPU-Hour Cost Calculator, AI Training Cost Calculator, or Model Serving Cost Calculator to estimate real compute costs from your own inputs.
Keep up with the market
Read the ComputeTape Morning Brief for daily AI compute pricing, power, capacity, and infrastructure signals — plus a different Compute College lesson highlighted each day.
Contact Compute College
Send lesson ideas, corrections, source material, or questions about AI compute education to the editorial team.