# Radeon PRO WX 9100: 16 GB with a versioned legacy specification

Radeon PRO WX 9100: official memory and board-power variants, ROCm and Blender Cycles support boundaries, and a practical workload validation scenario.

Author: Retrivium team
Updated: 2026-11-02
Canonical URL: https://retrivium.ai/journal/amd-radeon-pro-wx-9100-llm-rendering/
Language: en

Radeon PRO WX 9100 is officially listed with 16 GB HBM2; its current support page specifies 230 W board power. This legacy Vega card requires dates and sources when historical publications provide different data.

## Official variants and the memory boundary

The table follows [AMD materials for this model](https://www.amd.com/en/support/downloads/drivers.html/graphics/radeon-pro/radeon-pro-wx-x100-series/radeon-pro-wx-9100.html). It describes dedicated device memory, not system RAM. A “not verified” entry preserves a source gap; a neighboring configuration cannot supply the missing specification.

| AMD variant | Dedicated memory | Board power |
|---|---|---|
| [16 GB](https://www.amd.com/en/support/downloads/drivers.html/graphics/radeon-pro/radeon-pro-wx-x100-series/radeon-pro-wx-9100.html) | 16 GB HBM2 | 230 W |

## Establish the LLM software path

Radeon PRO WX 9100 is absent from the checked [ROCm Core SDK 10.1.0 GPU list](https://rocm.docs.amd.com/en/docs-10.1.0/about/release-notes.html). Support for a neighboring model cannot be transferred through a shared generation or a similar name. For a separate experiment, the [llama.cpp build documentation](https://raw.githubusercontent.com/ggml-org/llama.cpp/master/docs/build.md) describes a Vulkan backend. That route requires a suitable driver, detection of the actual device, and validation of the selected GGUF; Vulkan in a specification does not establish that every operation works. Save tensor-placement logs and compare output with a reference run before concluding that the GPU is actually involved. This is not a claim of current official ROCm support for this card.

## A practical scenario for this model

The scenario is reconstructing a workstation record from an old document whose specifications differ from the present AMD page. Separate document date, exact board implementation, and the power boundary first. This guide uses the currently verified 230 W field; it is not a measurement of the installed machine. If the actual board has other documentation, preserve the discrepancy until hardware identity is resolved instead of silently replacing one number with another. Tie software checks to a current backend version and saved model file as well. Previous operation of a professional application on WX 9100 cannot establish support for a current compute operation. A useful result separates historical specifications from the present experiment rather than mixing them into a universal compatibility claim.

## Validate Blender Cycles separately

Vega predates the RDNA 1 HIP hardware floor in the [Blender Cycles 5.2 LTS manual](https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html). It is therefore not a current Cycles HIP target; historical compute support or a ROCm LLM experiment cannot establish renderer eligibility.

Preserve an old scene original software route separately. Vega predates the current Cycles HIP hardware floor, so an archived frame cannot validate the current route.

## Preserve a machine-level acceptance record

The table gives AMD board-power specifications, not measured whole-computer consumption. Check the power supply, connectors, card dimensions, and airflow path for the actual system separately. Board power cannot establish inference speed.

Preserve WX 9100, 16 GB, the current 230 W source, and links to disputed historical data. Specification differences cannot be presented as calculated energy savings.

The acceptance artifact should connect board identity, software versions, model revision, and the workload actually exercised. After any of those changes, the old result describes its original run rather than establishing compatibility of the new configuration.

## Related reading

[vLLM or llama.cpp: serving workloads and GGUF workflows](/journal/vllm-vs-llama-cpp/); [Idle render farms: assessing a second GPU workload](/journal/render-farm-idle-gpus/); [NVIDIA and AMD GPU catalogue for LLM inference and server rendering](/journal/nvidia-amd-gpu-catalog/).