The AI Hypercomputer is a specialized system designed to handle heavy machine learning (ML) workloads by combining high-performance hardware with optimized software. Within this system, Vertex AI acts as a central platform to manage the entire ML lifecycle, from training models to serving them to users. By using these tools together, organizations can build and scale complex AI applications efficiently while keeping costs under control.
To handle large-scale training, Vertex AI custom training allows users to define specific hardware needs, such as the number of GPUs or TPUs. The system uses autoscaling to automatically adjust resources based on demand, ensuring that pipelines have enough power without wasting money. Key scaling features include horizontal autoscaling to adjust worker instances based on data processing needs, worker pools to set specific machine types and accelerators, and Spot VMs to provide a low-cost way to run tasks that can handle interruptions.
Serving models for user requests, known as inference, can be done through Vertex AI endpoints or serverless tools like Cloud Run. Cloud Run is particularly useful because it can scale to zero when not in use, which saves significant costs. It also supports GPU-enabled instances, making it a great choice for AI agents, quantized models, and real-time inference.
Maintaining high availability (HA) ensures that ML services remain online even if a part of the system fails. This is achieved by distributing deployments across multiple regions and using global endpoints to route traffic. For long training jobs, checkpointing is a vital concept that saves progress at regular intervals, allowing a job to resume quickly if a hardware failure occurs or if a Spot VM is reclaimed by Google Cloud.
Effective resource management involves using Cloud Monitoring to track how much power GPUs and TPUs are using. By analyzing this data, teams can forecast future demand and use Committed Use Discounts (CUDs) to lower prices for steady workloads. For more flexible needs, the Dynamic Workload Scheduler (DWS) helps obtain scarce hardware by queuing jobs until resources are ready. This proactive approach ensures that critical AI projects always have the compute power they need to succeed.
An AI Hypercomputer integrates specialized hardware like GPUs and TPUs to support large-scale model training and serving. Utilizing Google Kubernetes Engine (GKE) allows architects to manage these resources efficiently. This setup ensures that complex AI tasks have the necessary computing power to run smoothly.
To support these workloads, Hyperdisk provides scalable storage performance that can be adjusted based on demand. Architects use the Compute Engine Persistent Disk CSI driver to connect this storage to GKE clusters. This allows for dynamic updates to throughput and IOPS without interrupting the system, which improves operational efficiency, scalability, and flexibility across different machine types.
Managing scalability requires a Horizontal Pod Autoscaler (HPA) to adjust the number of active pods based on real-time needs. For AI workloads, two critical metrics are used to guide this process: num_requests_waiting and gpu_cache_usage_perc. Choosing the right metric depends on whether the goal is throughput optimization to handle more tasks at a lower cost, or latency sensitivity for faster response times.
Optimizing for different consumption models helps balance performance with budget constraints. Google Cloud offers various GPU types, such as the NVIDIA H100 or L4, to match specific workload requirements. Using Spot VMs can significantly reduce costs for tasks that are not time-critical, allowing organizations to run large-scale training while maintaining financial efficiency.
Architects use Terraform to automate the provisioning of regional clusters with GPU support. This ensures that infrastructure is consistent and can be recreated easily across different environments. Additionally, integrating Vertex AI and BigQuery allows for end-to-end ML workflows, including vector search and data analysis, which creates a unified platform for teams to collaborate.
To build a high-performance machine learning environment, you must choose the right accelerators based on your workload needs. Google Cloud offers various GPUs, such as the NVIDIA A100, and specialized TPUs for large-scale training. Using Terraform allows you to automate the creation of GKE clusters with specific GPU types and machine series like the A3 High or A4. You can also configure how drivers are installed, choosing between default, latest, or manual options to ensure hardware compatibility.
Achieving the best performance requires finding the right balance between throughput and latency. You should use load testing to create graphs that show how these two factors interact under different conditions. For many models, monitoring the KV-Cache Utilization helps determine the best settings for performance. This experimental approach ensures that you select a configuration that meets your specific speed and cost goals.
Scaling your infrastructure is handled through the Horizontal Pod Autoscaler (HPA), which adjusts resources based on real-time demand. To optimize for throughput and cost, the autoscaler can scale based on the number of waiting requests. Alternatively, latency-sensitive workloads can scale based on GPU cache utilization percentage to keep responses fast. Monitoring these metrics via Prometheus allows the system to add or remove nodes automatically.
To maximize the efficiency of your hardware, you should implement distributed training and mixed precision. Distributed training spreads the workload across multiple machines, while mixed precision reduces memory usage and speeds up processing. Tuning the batch size is a critical step to ensure your GPUs are fully utilized without causing out-of-memory errors. These techniques help you get the most value out of expensive hardware resources during the training phase.
For massive models, the AI Hypercomputer approach involves using Ray on GKE with TPU slices. You can define specific topologies, such as a 2x4 configuration, to optimize how the hardware communicates during training. Using Hyperdisk storage further scales performance by providing high-speed data access to the nodes, supporting the entire workflow from initial training to serving the model at scale.
Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
The AI Hypercomputer is a specialized system that combines high-performance hardware with optimized software to handle heavy machine learning workloads. Vertex AI acts as a central platform within this system to manage the entire ML lifecycle, from training models to serving them to users, enabling organizations to build and scale complex AI applications efficiently while controlling costs.
The Horizontal Pod Autoscaler uses two critical metrics for AI workloads: num_requests_waiting, which optimizes for throughput to handle more tasks at lower cost, and gpu_cache_usage_perc, which is used for latency-sensitive workloads to keep responses fast.
Checkpointing saves progress at regular intervals during long training jobs, allowing a job to resume quickly if a hardware failure occurs or if a Spot VM is reclaimed by Google Cloud. This ensures that time and compute resources are not wasted when interruptions happen.
Cloud Run can scale to zero when not in use, which saves significant costs for inference workloads. It also supports GPU-enabled instances, making it suitable for AI agents, quantized models, and real-time inference scenarios where flexibility and cost efficiency are priorities.
Spot VMs provisioning model
Future reservations in calendar mode
Standard on-demand provisioning model
Flex-start using Dynamic Workload Scheduler
An AI research team is deploying multi-node large language model (LLM) fine-tuning jobs that take between 3 and 5 days to complete. The workload has the following architectural requirements:
Which AI Hypercomputer consumption option should you recommend?