Intermediate

PyTorch on ROCm

A practical guide to pytorch on rocm within the amd rocm stack topic.

What This Lesson Covers

PyTorch on ROCm is a key topic within AMD ROCm Stack. In this lesson you will learn what it is, why it matters in production, the mechanics behind it, and the patterns experienced AI hardware engineers use. By the end you will be able to apply pytorch on rocm in real systems with confidence.

This lesson belongs to the GPU Software Stack category of the AI Hardware track. Hardware decisions compound massively at scale — a 10% throughput improvement on a 1000-GPU cluster pays for a small engineering team. The vendors and tools change fast, but the underlying principles (memory bandwidth, interconnect topology, precision tradeoffs, batching) are stable.

Why It Matters

Master ROCm — AMD's open-source GPU compute platform. Learn HIP, ROCm libraries, PyTorch on ROCm, and porting CUDA code to ROCm.

The reason pytorch on rocm deserves dedicated attention is that the difference between a well-utilized cluster and an idle one usually comes down to small decisions made here. Two teams running the same model on the same hardware can see 2-5x throughput differences depending on how well they execute on this technique. Understanding the underlying mechanics — not just running the vendor quick-start — is what lets you adapt when the defaults stop working at your scale.

💡
Mental model: Treat pytorch on rocm as a deliberate engineering decision, not a default. AI hardware workloads are unforgiving: a poor topology choice that costs 20% of bandwidth at 8 GPUs costs proportionally more at 8000 GPUs — and the marginal compute is the most expensive thing in your data center.

How It Works in Practice

Below is a worked example showing how to apply pytorch on rocm in real code. Read through it once, then experiment by changing the parameters and observing the effect on throughput, latency, memory, and cost.

// HIP version of vector add (drop-in CUDA replacement)
#include 
#include 

__global__ void vector_add(float *a, float *b, float *c, int n) {
    int i = blockIdx.x * blockDim.x + threadIdx.x;
    if (i < n) c[i] = a[i] + b[i];
}

int main() {
    const int N = 1 << 20;
    float *d_a, *d_b, *d_c;
    hipMalloc(&d_a, N * sizeof(float));
    hipMalloc(&d_b, N * sizeof(float));
    hipMalloc(&d_c, N * sizeof(float));

    int threads = 256;
    int blocks = (N + threads - 1) / threads;
    hipLaunchKernelGGL(vector_add, blocks, threads, 0, 0, d_a, d_b, d_c, N);
    hipDeviceSynchronize();
    return 0;
}
// Compile: hipcc --offload-arch=gfx942 vec_add.hip.cpp -o vec_add

Step-by-Step Walkthrough

  1. Verify your hardware — Run nvidia-smi (or vendor equivalent), check driver and SDK versions, confirm interconnect topology with nvidia-smi topo -m or ibstat. Hardware mismatches are the #1 cause of mysterious slowdowns.
  2. Pick the right precision — FP8/FP4 on Hopper/Blackwell, BF16/FP16 on Ampere, INT8 on edge. Mismatched precision wastes silicon you paid for.
  3. Profile before you optimize — Nsight Systems, NVIDIA NCU, AMD Omnitrace, or torch.profiler. You cannot improve what you have not measured.
  4. Tune one knob at a time — Batch size, tensor parallelism, pipeline parallelism, KV cache size. Changing five things at once leaves you guessing which one mattered.
  5. Validate cost-per-token, not just throughput — Higher peak FLOPS does not always mean lower $/token. Always measure end-to-end at your real workload.

When To Use It (and When Not To)

PyTorch on ROCm is the right tool when:

  • You have measured a real bottleneck that this technique addresses
  • The workload volume justifies the engineering effort to set it up properly
  • You have monitoring in place to detect regressions
  • The added complexity will earn its keep at your scale

It is the wrong tool when:

  • A simpler approach already meets your throughput and latency targets
  • You have not profiled and do not know where the bottleneck is
  • The added complexity will outlive your willingness to maintain it
  • You are still iterating on the model architecture — stabilize that first
⚠
Common pitfall: Engineers reach for pytorch on rocm before they have benchmarked the simplest possible approach. A well-tuned vLLM or TensorRT-LLM with default settings often beats a hand-optimized kernel by an engineer who has not profiled. Always measure first.

Production Checklist

  • Are GPU utilization, memory utilization, and SM occupancy monitored continuously?
  • Is interconnect bandwidth measured (NVLink, InfiniBand, PCIe) and not silently degraded?
  • Have you measured cost-per-token (or cost-per-training-step) at your real workload, not synthetic?
  • Do you have alerts for thermal throttling, ECC errors, and link drops?
  • Is there a runbook for the most common failure modes (driver crash, OOM, NCCL hang)?
  • Have you load-tested at 2-3x your projected peak to find the breaking point?

Next Steps

The other lessons in AMD ROCm Stack build directly on this one. Once you are comfortable with pytorch on rocm, the natural next step is to combine it with the patterns in the surrounding lessons — that is where compound returns kick in. Hardware skills are most useful as a system, not as isolated tricks.