Renting GPUs looks simple until you need 256 of them in one placement group next week. The providers differ less in which NVIDIA chip they offer than in how their instances are connected, how capacity is reserved, what managed file systems sit next to the GPUs, and how much of the cluster tooling you must build yourself. This course gives you a comparison method and the current facts to apply it.
You first learn to read an instance specification: GPUs, GPU memory, host memory, local NVMe, and scale-out bandwidth. You then compare the main families: AWS P5, P6-B200, P6-B300 and the P6e GB200/GB300 UltraServers with EFA; Azure ND H100/H200 v5, ND MI300X v5 and ND GB200/GB300 v6 with InfiniBand; Google Cloud A3, A4, A4X and A4X Max alongside TPUs; and Oracle's RDMA superclusters, followed by specialist clouds such as CoreWeave, Lambda, Nebius and Crusoe. The second half covers capacity mechanisms (on-demand, reservations, AWS Capacity Blocks for ML, Google's Dynamic Workload Scheduler, spot and committed spend), managed storage (FSx for Lustre, Azure Managed Lustre, Google Cloud Managed Lustre), and managed cluster layers (SageMaker HyperPod, AWS ParallelCluster, Azure CycleCloud, Google Cluster Director), ending with a scored provider selection exercise. Instance names change often, so every fact is dated to October 2026 and the method is built to be reused.