Estimate — sign in for exact rates.

 Trusted GPU & AI infrastructure since 2015 — Huntsville, AL
[email protected] Track order Support Log in
24 GB GDDR6 · RDNA 3 · gfx1100

AMD Radeon RX 7900 XTX 24GB

The RX 7900 XTX has 24 GB of GDDR6 memory. Its single-card candidate uses Qwen3.8-27B UD-Q4_K_M at a 32K catalog context; the 20 GB XT candidate uses another quantization and context. A raw speed comparison between those recipes would confound the cards with the model settings. A later comparison should hold artifact and workload fixed.

Two XTXs could split the Q8 candidate for capacity or run separate workers for simultaneous requests, but those are distinct configurations. Confirm each card’s free VRAM and actual PCIe connection, then measure completed work and response quality. No candidate on this page is a compatibility or performance promise.

AMD specifications

Recipes

Windows

Linux

How we test and measure →

Community reports — not measured or reproduced by Bitworks

Reported by others, linked to the original. Bitworks has not verified these numbers; they can differ on your system.

Reported on Reddit by ghosthand Original report

Not reproduced by Bitworks

Qwen3.8-27B on dual RX 7900 XTX with tensor split and MTP

Method (as reported): Author compared single-GPU non-MTP and dual-tensor MTP server rows with f16 KV and flash attention.

  • Reported GPU setup RX 7900 XTX
  • GPU count 2
  • Operating system Linux (Docker ROCm)
  • Environment Container
  • Engine llama.cpp server-rocm b10481 (25ae3a9b3)
  • Backend ROCm
  • Model Qwen3.8-27B UD-IQ4_XS
  • Configured context 131,072 tokens
  • Actual input 86,675 tokens
  • Full window tested no
  • Reported context Author also configured 262144; not the occupied depth in these rows.
  • Simultaneous clients 1
  • Workers 1
  • Topology dual-split (tensor split; PCIe 4.0 x16 CPU plus x4 chipset)
  • Speculative decoding MTP
  • CPU Ryzen 9 9950X
  • Memory configuration 96 GB reported; unit not verified
  • PCIe PCIe 4.0 x16 CPU plus x4 chipset
  • 69.25 tok/s — generation speed (per request) · API server · 1 client · input 86,675 tokens
    Compared with 29.28 tok/s (baseline single GPU/no MTP; reported dual tensor/MTP); changed between the two runs: GPU count, split mode, speculative decoding, context
    Same reported prompt; f16 KV, flash attention; baseline also changed context.
    This row: configured context: 131,072 tokens · speculative decoding: MTP · topology: dual-split · cards: 2
  • 361 tok/s — prompt speed (per request) · API server · 1 client · input 86,675 tokens
    Compared with 516 tok/s (single GPU without MTP vs dual tensor with MTP); changed between the two runs: GPU count, split mode, speculative decoding, context
    Same reported prompt; f16 KV, flash attention; baseline also changed context.
    This row: configured context: 131,072 tokens · speculative decoding: MTP · topology: dual-split · cards: 2

Not reported: system memory, artifact digest, sample count and variance, physical memory residency

  • UD-IQ4_XS differs from the linked Q8_0 recipe.
  • The comparison changes GPU count, split mode, MTP, and configured context; it does not isolate a speedup cause.
  • The larger configured window was not filled by the prompt.

Related reports from the same author or project — not independent replication

Reported on Reddit by nasone32 Original report

Not reproduced by Bitworks

Dual RX 7900 XTX tensor parallel on limited PCIe

Method (as reported): Author used rocprofv3 on a saturated chipset link and combined transfer compression with a larger patch set.

HEAD seen at retrieval: 15995a12d1d5 (not necessarily the commit the author measured)

  • Reported GPU setup RX 7900 XTX
  • GPU count 2
  • Operating system Linux (Ubuntu 24; ROCm 7.14)
  • Engine custom llama.cpp HIP fork
  • Backend ROCm
  • Model Qwen3.8-27B Q8_0
  • Actual input input length not reported
  • Reported context Prompt row has known input length; decode range may use another condition.
  • Workers 1
  • Topology dual-split (tensor split; one chipset-connected PCIe x4 card)
  • Speculative decoding adaptive MTP in decode range
  • PCIe one chipset-connected PCIe x4 card
  • ≈1400 tok/s — prompt speed (per request) · input 8,192 tokens
    Compared with 1100 tok/s (baseline patched AllReduce; reported Q8 transfer); changed between the two runs: engine build, other
    Approximate author comparison on the same asymmetric host.
    This row: topology: dual-split
  • ≈60–65 tok/s — generation speed (per request)
    Combined RDNA Boost and adaptive MTP patch set; not isolated transfer-only data.
    This row: speculative decoding: adaptive MTP · topology: dual-split

Not reported: configured context, simultaneous clients, CPU, system memory, exact tested fork commit, artifact digest, replications, quality delta, full launch arguments

  • Custom patch set differs from the linked recipe and is not a stock Windows path.
  • Same author and host as the topology report; not an independent replication.
  • Author had not evaluated quality impact of Q8 inter-card transfer.
  • Fork author says combined build will not be maintained.

Setup guide (external)

Related link (external)

Reported on Reddit by nasone32 Original report

Not reproduced by Bitworks

Notes on dual RX 7900 XTX tensor split topology

Method (as reported): Author compared layer and patched tensor split on an asymmetric dual-card host; exact test counts not supplied.

  • Reported GPU setup RX 7900 XTX
  • GPU count 2
  • Operating system Linux (ROCm Linux; Windows failure also described)
  • Engine custom llama.cpp HIP
  • Backend ROCm
  • Model Qwen3.8-27B Q8_0
  • Actual input input length not reported
  • Workers 1
  • Topology dual-split (PCIe 4.0 x16 CPU plus x4 chipset)
  • Speculative decoding MTP3 in generation comparison
  • PCIe PCIe 4.0 x16 CPU plus x4 chipset
  • ≈1150 tok/s — prompt speed (per request)
    Compared with 1500 tok/s (baseline layer split; reported patched tensor split); changed between the two runs: split mode, engine build
    Approximate author-reported comparison on asymmetric PCIe topology.
    This row: topology: dual-split
  • ≈50 tok/s — generation speed (per request)
    Compared with 30 tok/s (baseline layer split; reported patched tensor/MTP3); changed between the two runs: split mode, engine build, speculative decoding
    Approximate prose comparison; split and speculation both changed.
    This row: speculative decoding: MTP3 · topology: dual-split

Not reported: configured context, actual input length, simultaneous clients, CPU, system memory, exact build and patch digest, prompt and output counts, repetition and variance, Windows version and driver

  • Custom internal AllReduce runtime differs from the linked recipe.
  • The generation comparison changes both split and MTP settings.
  • Author-reported Windows P2P failure does not establish a native-Windows tensor recipe.
  • Predicted symmetric-slot gains are not measurements.

Reported on GitHub by Niko1221 / Strata maintainers Original report

Not reproduced by Bitworks Project documentation — capability, not a measurement

Strata AMD HIP guide

Method (as reported): Maintainer documents Windows bundled HIP runtime, per-card checks and Linux layer split; no discrete AMD Windows model-load validation.

HEAD seen at retrieval: 6f32ec070f23 (not necessarily the commit the author measured)

  • Reported GPU setup Windows: one GPU per model; Linux: selectable layer split
  • GPU count not reported
  • Operating system Windows and Linux (Windows HIP and Linux HIP)
  • Engine Strata HIP
  • Backend HIP
  • Model Qwen3.8-Flash-Next pack
  • Actual input input length not reported
  • Topology not reported — Windows one GPU per model; Linux selectable layer split

Not reported: model quantisation, configured context, actual input length, simultaneous clients, topology, CPU, system memory, release archive digest and revision, Windows discrete-card load, Windows dual-card execution, quality and memory curves

  • Maintainer says ready-made Windows archive has not run a model on a discrete AMD card in documented validation.
  • Capability documentation, not a measured compatibility or performance result.
  • RX 9060 XT memory variant is unspecified in the guide, so neither variant is mapped.

Setup guide (external)

No approved community measurement is shown here for:

  • Native Windows

Discussion

Share setups, questions and your own results. Posts are reviewed before they appear. Replies from Bitworks staff are marked.

Log in Create an account to join the discussion.

Bitworks listings for this card

Select the fields to be shown. Others will be hidden. Drag and drop to rearrange the order.
  • Image
  • SKU
  • Rating
  • Price
  • Stock
  • Availability
  • Add to cart
  • Description
  • Content
  • Weight
  • Dimensions
  • Additional information
Click outside to hide the comparison bar
Compare
Compare ×
Let's Compare! Continue shopping