Compute Tiers for AI Architecture Intermediate

A well-designed compute tier strategy ensures that every AI workload runs on the most cost-effective infrastructure that meets its performance requirements. This lesson covers how to architect multi-tier compute hierarchies that balance GPU availability, cost efficiency, and operational simplicity.

The Four Compute Tiers

Tier Resources Workloads Cost Profile
Tier 1: HPC GPU H100/A100 clusters with NVLink Large model training, distributed training $$$$ (reserved or on-demand)
Tier 2: Standard GPU A10G, L4, T4 instances Fine-tuning, small model training, inference $$ (spot + on-demand mix)
Tier 3: CPU Compute High-memory CPU instances Data preprocessing, feature engineering, CPU inference $ (spot-friendly)
Tier 4: Serverless Lambda, Cloud Functions, Cloud Run Lightweight inference, event-driven processing Pay-per-use

GPU Pool Architecture

Centralized GPU pools shared across teams provide better utilization and cost efficiency than dedicated instances:

  • Kubernetes GPU scheduling - Use node selectors and tolerations to route workloads to the right GPU tier
  • GPU time-slicing - Share a single GPU across multiple inference workloads using MPS or MIG
  • Priority queuing - Implement priority-based scheduling so production inference takes precedence over training experiments
  • Quota management - Set per-team GPU quotas to prevent resource monopolization

Scaling Strategies by Tier

  • Tier 1 - Pre-provisioned reserved capacity. Scale by adding nodes to the training cluster. Use checkpointing for fault tolerance.
  • Tier 2 - Cluster autoscaler with mixed on-demand and spot instances. Scale based on pending pod count.
  • Tier 3 - Aggressive spot usage (90%+). Scale based on queue depth or CPU utilization.
  • Tier 4 - Automatic scaling to zero. No capacity planning required.
Design Pattern: Use the "tier waterfall" pattern: attempt to schedule on the cheapest tier first, and cascade up to more expensive tiers only when the cheaper option cannot meet the workload's requirements.

Ready to Architect Data Pipelines?

The next lesson covers data ingestion, lake storage, feature stores, and streaming pipelines for ML.

Next: Data Pipeline →

Ready to Go Deeper?

Live instructor-led courses from our partners. Affiliate disclosure.