In this article
gfx908 ROCm support is real evidence; it is not automatic Cycles HIP eligibility.
AMD Instinct MI100 is assessed here as an exact CDNA 1 board configuration. Its published 32 GB capacity is the starting point for a workload qualification, not a measured serving or rendering result.
Exact model and memory variants
MI100 is a 32 GB HBM2 CDNA accelerator with a 300 W server-card envelope. The current ROCm10.1 matrix explicitly retains the MI100 gfx908 target.
| Variant | Memory | Published board power | Cooling / format |
|---|---|---|---|
| MI100 | 32 GB HBM2 | 300 W | Passive; PCIe server card |
Specifications: Official product/support documentation.
LLM backend and memory budget
The gfx908 entry establishes a supported ROCm stack, not every engine or quantization kernel. Align OS, driver and user-space components, then validate chosen weights with concrete context and working buffers.
A ROCm support entry does not certify every inference engine, model kernel or quantization format.
Compatibility evidence: ROCm compatibility matrix.
Cycles and batch rendering
CDNA is not RDNA. The published Cycles HIP path requires RDNA1 or newer, so MI100 membership in ROCm does not certify standard Cycles5.2 HIP rendering support.
Blender 5.2 LTS GPU rendering manual.
Integration into a server or workstation
Retain the supported OS/kernel/driver combination from the checked ROCm matrix. The passive compute card requires a suitable server configuration. A successful HIP compute operation is useful inference-stack evidence but cannot stand in for a render-engine hardware eligibility check.
A concrete qualification scenario
A lab inherits MI100 and assumes that old age means all current software support disappeared. Verify the explicit gfx908 entry, reproduce the supported stack and qualify one fixed inference artifact. Keep any missing model-kernel support as a separate result. For a proposed Cycles service, record the CDNA-versus-RDNA eligibility boundary instead of interpreting ROCm detection as a successful renderer test. The record preserves both a real compute opportunity and its documented rendering limitation.
The evidence to retain
Keep an ordinary qualification record with the actual test outputs.
Identify the tested variant, software build and execution mode before entering observations. Leave unavailable measurements explicitly unknown.
The fields below separate published specifications from observed allocation and job completion, so a later operator can repeat the same case.
| Evidence field | What this profile must retain |
|---|---|
| Hardware identity | AMD Instinct MI100; physical variant and reported device identifier |
| Memory boundary | 32 GB published; observed free memory before and after loading |
| Inference artifact | Exact weights digest, quantization, context and offload configuration |
| Render artifact | Scene digest, renderer version, backend and denoising setting |
| System envelope | Driver, container/build digest, enclosure and cooling configuration |
| Completion evidence | Application exit status, output validity and observed memory failures |
A gfx908 support entry and a successful model kernel are different evidence layers; retain the exact supported operating-system stack too.
Further reading: RAM and VRAM: which memory matters for an AI server?, A GPU inference benchmark you can trust, NVIDIA and AMD GPU catalogue.