Radeon RX 9070 XT vs RTX PRO 6000 Blackwell

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT✓fullprobed8/10

   A direct probe confirms rocm.docs.amd.com/llms.txt returns HTTP 200 with structured content pointing to sub-project docs, giving an agent a genuine machine-readable entry point into the Radeon/ROCm software docs relevant to this GPU. Missing for 10: no evidence of llms.txt coverage at finer granularity (e.g., per-page) and no OpenAPI/agent API surface (which 404s), so agentic doc access is present but not comprehensive.

   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rocm.docs.amd.com/openapi.json, https://rocm.docs.amd.com/swagger.json, https://rocm.docs.am…”
   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell~partialprobed6/10

   A probe confirms developer.nvidia.com/llms.txt returns HTTP 200 with a description of NVIDIA's developer portal, showing an agent could be pointed at an llms.txt-style resource covering NVIDIA's AI/dev ecosystem. However this is a generic NVIDIA-wide file, not RTX PRO 6000-specific, and companion probes (docs-md, openapi) 404, indicating no broader agent-oriented documentation surface. Missing for 10: product-specific agent-readable docs, markdown/API doc mirrors, and any first-party mention of llms.txt support.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.nvidia.com/llms.txt # NVIDIA Developer > Comprehensive developer portal for NVIDIA accelerate…”
   • [probe] “PROBE docs-md: HTTP 404 at https://developer.nvidia.com/cuda-toolkit.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.nvidia.com/openapi.json, https://developer.nvidia.com/swagger.json, https://develo…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialclaimed4/10

   Evidence shows ROCm/Linux support with PyTorch, vLLM, and Llama.cpp for compute workloads (amd-rx-9070-xt-docs-2, -10, -11), which implies the GPU can be used for automated inference/training pipelines without a display, but there is no explicit documentation of headless operation, Docker/CI runner support, or automation-specific tooling. Missing for 10: explicit headless-mode docs, CI/container integration guides, and any hands-on evidence of running in automated pipelines.

   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The evidence describes local desktop AI workflows, CUDA toolkit, and MIG partitioning, but nothing addresses running the GPU headlessly (no display) in a CI/automation pipeline. Since GPUs are commonly deployed headlessly in server/CI environments, the axis applies, but no evidence of headless operation, driver support without display, or CI integration is provided.

   ⚑ flag

3. ai-native userUse an official CLI

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   Evidence describes CUDA toolkit components (compiler, libraries, debugging tools) but never explicitly documents an official CLI tool (e.g., nvidia-smi or similar) for AI-native/agentic workflows tied to this GPU.

   ⚑ flag

4. ai-native userDrive the product through a documented public API

   weight 3 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialprobed4/10

   AMD documents a public software stack (ROCm) with APIs/libraries (HIP, PyTorch/TensorFlow/JAX/ONNX/vLLM/llama.cpp integration) that let developers programmatically drive the GPU for AI workloads, and llms.txt is served for documentation discovery. However, there is no dedicated machine-callable REST/OpenAPI interface — the openapi probe returned 404 on all candidate paths — so an AI agent cannot invoke a structured public API directly, only use ROCm's compiled libraries/frameworks. Missing for 10: a documented REST/OpenAPI or similarly agent-consumable API endpoint, independent confirmation of programmatic control beyond framework bindings.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rocm.docs.amd.com/openapi.json, https://rocm.docs.amd.com/swagger.json, https://rocm.docs.am…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   Evidence documents CUDA as a programming toolkit for writing GPU-accelerated software, but there is no documented public API for programmatically 'driving' the RTX PRO 6000 itself (e.g., management/control API for agentic automation), and probes explicitly found no OpenAPI/swagger spec (404s) for the developer portal.

   • [claimed-docs] “The toolkit includes GPU-accelerated libraries, debugging and optimization tools, a C/C++ compiler, and a runtime library.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.nvidia.com/openapi.json, https://developer.nvidia.com/swagger.json, https://develo…”
   • [probe] “PROBE docs-md: HTTP 404 at https://developer.nvidia.com/cuda-toolkit.md”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT✓fullprobed7/10

   AMD provides official ROCm SDK documentation for the RX 9070 XT enabling development with PyTorch, TensorFlow, JAX, ONNX, vLLM, and llama.cpp on both Windows and Linux, with an llms.txt confirming machine-readable docs availability. Missing for 10: independent hands-on developer confirmation of SDK stability/completeness, and no evidence of API/openapi endpoints for programmatic integration.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell~partialcommunity6/10

   NVIDIA provides well-documented official SDKs to build against (CUDA Toolkit with compiler/runtime/libraries, cuTile Python, RTX Neural Shaders SDK) that target this GPU's architecture, giving AI-native developers a real path to build agentic/AI workloads. However, community hands-on discussion notes the card's SM120 architecture lacks support for key CUDA primitives (tmem/tcgen05) in main libraries, indicating real gaps in SDK/library readiness beyond the marketing claims. Missing for 10: independent developer corroboration of successful SDK integration, resolution of the SM120 library-support gap, and clearer documentation of which SDK features are actually usable on this specific card.

   • [claimed-docs] “The toolkit includes GPU-accelerated libraries, debugging and optimization tools, a C/C++ compiler, and a runtime library.”
   • [claimed-docs] “cuTile Python is an expression of the CUDA Tile programming model in Python. It is built on top of the CUDA Tile IR specification and allows…”
   • [claimed-docs] “The RTX Neural Shaders SDK lets developers train shader data on an RTX PRO workstation and accelerate neural representations with NVIDIA Ten…”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Radeon RX 9070 XT—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Inference stack

1. ai-native userThis GPU has a documented LLM inference story — low-precision formats (FP8/FP4) and supported serving stacks (TensorRT-LLM, vLLM, ROCm, llama.cpp) for this part

   weight 3 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialclaimed5/10

   ROCm docs explicitly document serving-stack support for this Radeon line (vLLM 'Full support', llama.cpp 'Supported for efficient inference', plus PyTorch/TensorFlow/JAX/ONNX), but there is no mention of low-precision FP8/FP4 inference formats for the RX 9070 XT, and TensorRT-LLM is an NVIDIA-only stack so is not applicable here. Missing for 10: explicit FP8/FP4 quantization support documentation for this card, independent hands-on benchmarks confirming these serving stacks actually run well on RX 9070 XT.

   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell!disputedcontradicted4/10

   NVIDIA's docs only vaguely reference AI/LLM use (memory capacity, CUDA-X libraries) without naming FP8/FP4 precision support or specific serving stacks like TensorRT-LLM, vLLM, ROCm, or llama.cpp for this part. Community evidence shows real inference throughput (41k tok/s) but also a concrete technical objection that the card's SM120 architecture lacks tmem/tcgen05 and has 'lack of support in main libraries', directly contradicting a clean 'supported serving stack' story. Missing for 10: explicit vendor documentation naming FP8/FP4 support and specific serving-stack compatibility (TensorRT-LLM, vLLM, llama.cpp), and resolution of the community-reported library support gaps.

   • [claimed-docs] “With 96 GB of memory on the RTX PRO 6000, you can turn your desktop into an AI powerhouse for fine-tuning LLMs, generative AI, and running a…”
   • [community] “Converting four RTX PRO 6000 Blackwell cards to waterblocks, finding a VRM choke loose on the workbench, and getting back to 41k tok/s.”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”

   proof ↗⚑ flag

Tensor specs

1. ml engineerSize training and inference from published tensor throughput — TFLOPS or TOPS with precision and sparsity stated, not a bare marketing number

   weight 3 · round drawn
   Radeon RX 9070 XT—none0/10

   The evidence pack covers ROCm software support, framework compatibility, and general features, but contains no published TFLOPS/TOPS figures for the RX 9070 XT with precision (FP16/FP32/INT8) or sparsity stated. Missing for 10: any tensor throughput numbers, precision breakdown, sparsity conditions, or comparison to a baseline needed for training/inference sizing.

   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”
   • [claimed-docs] “AV1 Decode Yes AV1 Encode Yes”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The evidence pack contains only generic marketing claims (96GB memory, CUDA-X libraries, PCIe Gen5, display specs) and community pricing/power discussions, but no published TFLOPS/TOPS figures broken out by precision (FP16/FP8/INT8) or sparsity state anywhere in the docs or community threads. A GPU spec sheet is exactly the kind of product where such throughput tables are expected, so the axis applies but is unmet.

   • [claimed-docs] “With 96 GB of memory on the RTX PRO 6000, you can turn your desktop into an AI powerhouse for fine-tuning LLMs, generative AI, and running a…”
   • [claimed-docs] “With 96 GB of GPU memory, tackle massive 3D and AI projects, explore large-scale VR environments, and drive larger multi-app workflows.”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Media engines

1. creatorHardware media engines and creator-app acceleration are documented — AV1/HEVC encoders, and professional or ISV-certified driver support where the vendor claims it

   weight 2 · round to RTX PRO 6000 Blackwell
   Radeon RX 9070 XT~partialclaimed4/10

   AMD's product page explicitly documents AV1 encode/decode support for the RX 9070 XT, which is relevant to creator workflows, but there is no mention of HEVC encode/decode support, no ISV-certified professional driver program (that's typically reserved for Radeon Pro cards), and no explicit creator-app acceleration claims (e.g., Premiere, DaVinci Resolve, OBS integration). Missing for 10: HEVC encoder/decoder documentation, ISV/professional certification claims, named creator-app acceleration partnerships or benchmarks.

   • [claimed-docs] “AV1 Decode Yes AV1 Encode Yes”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell~partialclaimed6/10

   Vendor docs explicitly claim enhanced AV1/H.265 (HEVC) encode/decode support aimed at livestreaming and real-time editing, plus general creator-app acceleration (3D modeling, animation, virtual production). However, there is no ISV-certification detail (no Studio driver or specific creative-app certification list) and no independent/hands-on verification of media-engine performance for creators. Missing for 10: ISV-certified driver documentation (e.g., Studio Driver certifications for specific creative apps), independent benchmarks of AV1/HEVC encode quality, and confirmation of number/type of NVENC/NVDEC engines.

   • [claimed-docs] “With enhanced AV1 and H.265 codec support, it's ideal for livestreaming, real-time editing, and live media workflows.”
   • [claimed-docs] “These advancements accelerate 3D modeling, animation, and virtual production, empowering industries like film, gaming, and architectural vis…”

   proof ↗⚑ flag

Scale out

1. ml engineerTrain and serve at datacenter scale on this part — documented high-bandwidth interconnect (NVLink, Infinity Fabric), multi-GPU systems, and rack-scale deployment

   weight 3 · round drawn
   Radeon RX 9070 XT—none0/10

   The evidence only shows ROCm software compatibility and a vague note that the same stack 'also supports' Instinct/CDNA datacenter accelerators, but nothing documents NVLink/Infinity Fabric interconnect, multi-GPU scaling, or rack-scale deployment for the RX 9070 XT itself, which is a single consumer desktop card without such interconnects. missing for 10: any documentation of multi-GPU interconnect (NVLink/Infinity Fabric) for this card, multi-GPU system support, rack-scale deployment guidance.

   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”
   • [claimed-docs] “This unified platform creates a seamless migration path, allowing you to develop applications locally and deploy them at scale with confiden…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The evidence pack contains no documentation of NVLink, Infinity Fabric, or any high-bandwidth multi-GPU interconnect for the RTX PRO 6000; it is positioned as a single-card workstation GPU (PCIe Gen5, desktop form factor) rather than a rack-scale datacenter part. Community threads even contrast it unfavorably with true datacenter GPUs (e.g., B300) citing lack of tensor-memory/library support and treat multi-card setups as just several discrete cards drawing 2.4kW, not a unified interconnect fabric.

   • [claimed-docs] “Support for PCI Express Gen 5 provides double the bandwidth of PCIe Gen 4, improving data-transfer speeds from CPU memory and unlocking fast…”
   • [community] “Ok, how are people powering these things? 2.4kW is well beyond a standard circuit in the US. Are people having 240V/30A circuits installed?”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”

   proof ↗⚑ flag

Linux support

1. developerLinux is a first-class citizen for this GPU — documented Linux driver releases and independent Linux testing of this part

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialclaimed6/10

   AMD's official docs explicitly list Linux x86-64 as a supported OS and provide detailed ROCm Linux documentation for PyTorch/TensorFlow/JAX/ONNX, vLLM, and llama.cpp on Radeon 9000-series GPUs, showing genuine first-class Linux driver/software support. However, the pack lacks independent hands-on Linux testing or benchmarks of the RX 9070 XT specifically (the only community citation is a general Windows-oriented performance review, not Linux-focused). Missing for 10: independent/third-party Linux driver stability or performance testing of this specific card, and any community confirmation of ROCm functionality on this GPU outside vendor docs.

   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “As a primarily open-source ecosystem, ROCm™ gives you the freedom to inspect, customize, and tailor the software stack to your specific need…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   No evidence in the pack specifically documents Linux driver releases or independent Linux benchmarking/testing of the RTX PRO 6000; the docs cite CUDA toolkit generically (cross-platform) and community threads discuss pricing, power draw, and hardware defects rather than Linux driver support or Linux-specific testing.

   ⚑ flag

Open drivers

1. developerRun this GPU on an open driver — open-source kernel modules or upstream Linux support documented by the vendor

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialclaimed6/10

   AMD documents ROCm as a primarily open-source stack with Linux support and lists RX 9000-series compatibility, and Linux x86 64-bit OS support is confirmed, but there is no explicit vendor documentation of open-source kernel driver components (e.g., amdgpu upstream kernel module) specific to RX 9070 XT or a clear statement of which parts of the stack are closed-source firmware/blobs. missing for 10: explicit vendor confirmation of upstream open-source kernel module support for this specific GPU, independent/hands-on corroboration of open driver functioning on mainline Linux kernels.

   • [claimed-docs] “As a primarily open-source ecosystem, ROCm™ gives you the freedom to inspect, customize, and tailor the software stack to your specific need…”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   No evidence in the pack mentions open-source kernel modules, nouveau, or upstream Linux driver support for the RTX PRO 6000; all docs cite proprietary CUDA/RTX toolkits and community discussion focuses on power, pricing, and hardware defects rather than driver openness. Missing for 10: any vendor documentation of open-source GPU kernel modules or upstream kernel support for this card.

   ⚑ flag

4k gaming

1. gamerThis card drives high-refresh 4K gaming — vendor performance claims corroborated by independent game benchmarks

   weight 3 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialcommunity3/10

   Only one independent source (TechPowerUp) confirms the RX 9070 XT delivers competitive raster/ray-tracing performance versus similarly priced NVIDIA cards, but it doesn't specifically address 4K high-refresh benchmarks or vendor FPS claims. Missing for 10: explicit vendor 4K/144Hz+ performance claims, detailed independent 4K benchmark numbers across multiple games, and confirmation of sustained high-refresh framerates.

   • [community] “The RX 9070 XT offers competitive performance with similarly priced NVIDIA options in both raster and ray tracing, at a starting price of $6…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Upscaling

1. gamerAI upscaling and frame generation are supported on this card — the DLSS or FSR generation is documented for this part, with broad game support

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialcommunity5/10

   AMD's product page confirms FSR ("Redstone") support on the RX 9070 XT, and third-party review corroborates strong raster/ray-tracing performance, but the evidence pack lacks detail on frame-generation specifics or a documented list of supported games. missing for 10: explicit frame-generation (FSR 3/4) feature naming, game compatibility list/count, independent hands-on upscaling benchmarks.

   • [claimed-docs] “AMD FSR™ "Redstone"”
   • [community] “The RX 9070 XT offers competitive performance with similarly priced NVIDIA options in both raster and ray tracing, at a starting price of $6…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The evidence pack covers workstation/AI/data-science features, memory, connectivity, and CUDA tooling, but never mentions DLSS, FSR, frame generation, or game-specific driver/game support for the RTX PRO 6000. This is a plausible axis for any RTX-branded GPU, so absence of documentation is 'none' rather than 'na'. missing for 10: DLSS/FSR version support documentation, frame generation capability, game compatibility list or driver notes.

   ⚑ flag

Llm memory

1. ai-native userRun a 70B-class quantized LLM on this GPU — published VRAM capacity and memory bandwidth that make local or single-node inference practical

   weight 3 · round to RTX PRO 6000 Blackwell
   Radeon RX 9070 XT—none0/10

   The evidence pack never states the RX 9070 XT's actual VRAM capacity or memory bandwidth; the one VRAM figure mentioned ("up to 48GB") is a generic Radeon workstation-GPU claim, not this card's spec, and there is no claim or benchmark showing a 70B-class quantized model running on this GPU. Software support (ROCm, vLLM, llama.cpp) is documented but doesn't substitute for the missing capacity/bandwidth evidence needed to judge practicality for 70B inference.

   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “A local workstation equipped with a Radeon™ GPU, featuring up to 48GB of VRAM, offers a secure and economical alternative to relying solely …”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell✓fullcommunity8/10

   NVIDIA docs explicitly market the 96 GB GDDR7 memory as enabling local LLM fine-tuning and agent workloads, and community evidence (HN thread) shows real users running multi-GPU RTX PRO 6000 setups for high-throughput LLM inference (tens of thousands of tok/s), confirming practical single-node large-model inference. Missing for 10: an explicit published memory-bandwidth (GB/s) figure and a documented single-card 70B-quantized benchmark rather than a 4-GPU aggregate.

   • [claimed-docs] “With 96 GB of memory on the RTX PRO 6000, you can turn your desktop into an AI powerhouse for fine-tuning LLMs, generative AI, and running a…”
   • [claimed-docs] “With 96 GB of GPU memory, tackle massive 3D and AI projects, explore large-scale VR environments, and drive larger multi-app workflows.”
   • [community] “Converting four RTX PRO 6000 Blackwell cards to waterblocks, finding a VRM choke loose on the workbench, and getting back to 41k tok/s.”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”

   proof ↗⚑ flag

Memory spec

1. ml engineerMemory specs are published in full for this exact part — capacity, memory type, bus width, and bandwidth

   weight 2 · round to RTX PRO 6000 Blackwell
   Radeon RX 9070 XT—none0/10

   Evidence pack contains no VRAM capacity, memory type (GDDR6), bus width, or bandwidth figures for the RX 9070 XT—only ROCm software ecosystem claims and generic product page snippets unrelated to memory specs.

   ⚑ flag

   RTX PRO 6000 Blackwell~partialcommunity4/10

   Official NVIDIA pages confirm 96GB GPU memory capacity clearly, but the evidence pack contains no first-party bus-width or bandwidth figures, and memory type (GDDR7) is only mentioned in a community comment, not vendor spec docs. missing for 10: bus width spec, bandwidth (GB/s) spec, vendor-confirmed memory type in official docs.

   • [claimed-docs] “With 96 GB of memory on the RTX PRO 6000, you can turn your desktop into an AI powerhouse for fine-tuning LLMs, generative AI, and running a…”
   • [claimed-docs] “With 96 GB of GPU memory, tackle massive 3D and AI projects, explore large-scale VR environments, and drive larger multi-app workflows.”
   • [community] “RTX Pro 6000 Blackwell has 96GB of GDDR7 VRAM. A Mac studio with 96GB unified memory costs $5,299.00... Why does CUDA still have a $11k pric…”

   proof ↗⚑ flag

1. ai-native userRead the product's source under an open license

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialprobed5/10

   AMD's ROCm docs claim the stack is a 'primarily open-source ecosystem' giving users freedom to inspect and customize the software, and this is corroborated by an accessible llms.txt docs endpoint, but this is the accompanying software stack, not the GPU's actual hardware/firmware source, and 'primarily' implies some closed-source components remain undisclosed. Missing for 10: explicit repository/license pointer for the actual open-sourced source code, confirmation of what portions (drivers, firmware) are closed, and independent hands-on verification of source availability.

   • [claimed-docs] “As a primarily open-source ecosystem, ROCm™ gives you the freedom to inspect, customize, and tailor the software stack to your specific need…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

2. ai-native userSelf-host the core product

   weight 3 · round drawn
   Radeon RX 9070 XT✓fullclaimed7/10

   As a discrete GPU, the RX 9070 XT is inherently self-hosted hardware; AMD's docs explicitly position a local Radeon workstation as a secure, economical alternative to cloud-based AI solutions, backed by open ROCm stack support for PyTorch/TensorFlow/JAX/ONNX/vLLM/llama.cpp on both Windows and Linux. Missing for 10: independent hands-on validation of a fully self-hosted AI stack setup, and more detailed first-party self-hosting/deployment guides beyond general ROCm docs.

   • [claimed-docs] “A local workstation equipped with a Radeon™ GPU, featuring up to 48GB of VRAM, offers a secure and economical alternative to relying solely …”
   • [claimed-docs] “This unified platform creates a seamless migration path, allowing you to develop applications locally and deploy them at scale with confiden…”
   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell✓fullcommunity7/10

   The RTX PRO 6000 is a physical GPU designed explicitly for local, on-premises AI workloads—running LLMs, agents, and data science locally 'without relying on costly cloud or data center resources,' with community evidence confirming real users self-hosting multi-GPU inference rigs achieving high token throughput. This is inherently self-hostable since it's hardware you own and run yourself. missing for 10: no first-party self-hosting guide/reference architecture, no independent benchmark validating claimed ease of self-hosted deployment at scale, and community notes highlight real friction (power/cooling requirements, hardware defects) that complicate the self-hosting experience.

   • [claimed-docs] “With 96 GB of memory on the RTX PRO 6000, you can turn your desktop into an AI powerhouse for fine-tuning LLMs, generative AI, and running a…”
   • [claimed-docs] “the NVIDIA RTX PRO 6000 accelerates data science workflows—from exploration and model evaluation to visualization—without relying on costly …”
   • [community] “Converting four RTX PRO 6000 Blackwell cards to waterblocks, finding a VRM choke loose on the workbench, and getting back to 41k tok/s.”
   • [community] “Ok, how are people powering these things? 2.4kW is well beyond a standard circuit in the US. Are people having 240V/30A circuits installed?”

   proof ↗⚑ flag

Efficiency

1. ml engineerSustained workloads are power-efficient on this part — documented power envelopes with independent performance-per-watt testing

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   Evidence covers ROCm software support, framework compatibility, and general GPU features, but there is no documented power envelope data or independent performance-per-watt testing for sustained ML workloads on this card. missing for 10: TDP/power envelope specs for sustained ML loads, independent perf-per-watt benchmarks, thermal/power throttling behavior under long-running compute jobs.

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The evidence pack contains no documented power envelope specs (TDP) from NVIDIA nor any independent performance-per-watt benchmarking; community discussion only raises concerns about high power draw (~600W/card implied from a 2.4kW quad-card setup) without any efficiency testing. Axis applies to a workstation GPU aimed at ML engineers, but no supporting evidence exists.

   • [community] “Ok, how are people powering these things? 2.4kW is well beyond a standard circuit in the US. Are people having 240V/30A circuits installed?”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”

   proof ↗⚑ flag

Psu planning

1. gamerSpec a build around published board power — TDP/TGP, connector requirements, and cooling guidance for this exact card

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   The evidence pack covers ROCm/software ecosystem support, AMD Software features, and general performance comparison, but contains no mention of TDP/TGP figures, PCIe power connector requirements, or cooling/case guidance for the RX 9070 XT. This is a fair axis for a discrete GPU, but nothing in the pack substantiates it.

   ⚑ flag

   RTX PRO 6000 Blackwell—none0/10

   The evidence pack contains only marketing copy about memory, CUDA-X, ray tracing, and I/O, with no official TDP/TGP figures, power-connector specifications, or cooling guidance for the RTX PRO 6000. Community threads mention very high real-world power draw (2.4kW across four cards) and cooling/VRM issues, but these are anecdotal complaints, not published board-power specs a gamer could use to plan a PSU or case cooling.

   • [community] “Ok, how are people powering these things? 2.4kW is well beyond a standard circuit in the US. Are people having 240V/30A circuits installed?”
   • [community] “Converting four RTX PRO 6000 Blackwell cards to waterblocks, finding a VRM choke loose on the workbench, and getting back to 41k tok/s.”

   proof ↗⚑ flag

1. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to RTX PRO 6000 Blackwell
   Radeon RX 9070 XT—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   RTX PRO 6000 Blackwell~partialclaimed3/10

   The product is a local workstation GPU, and NVIDIA markets it as enabling AI workloads to run 'locally and securely' without sending data to the cloud, which implicitly prevents data from being sent to a third party for training. However, there is no explicit privacy-control feature, data-usage policy, or opt-out mechanism documented — the claim is only an indirect byproduct of local compute. Missing for 10: an explicit data-training opt-out or privacy policy statement, independent confirmation that no telemetry/data leaves the device, and any documentation addressing data governance for AI workloads.

   • [claimed-docs] “With 96 GB of memory on the RTX PRO 6000, you can turn your desktop into an AI powerhouse for fine-tuning LLMs, generative AI, and running a…”

   proof ↗⚑ flag

Compute stack

1. developerShip GPU-compute workloads on the vendor's toolchain — CUDA or ROCm/HIP documentation lists this part as a supported target

   weight 3 · round drawn
   Radeon RX 9070 XT✓fullclaimed8/10

   ROCm documentation explicitly lists RX 9000 series (including 9070 XT) as a supported target on both Windows and Linux, with PyTorch, TensorFlow, JAX, ONNX, vLLM, and Llama.cpp support, plus a stated migration path to AMD Instinct datacenter GPUs. missing for 10: independent hands-on developer corroboration of ROCm workflows on this specific card beyond vendor docs, and no mention of CUDA compatibility layer maturity/limitations.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell✓fullprobed8/10

   NVIDIA's official CUDA Toolkit and CUDA-X docs explicitly list this GPU class as a supported target, and community usage (41k tok/s LLM inference) confirms real-world CUDA workload deployment. A minor caveat exists: one hands-on report notes SM120 lacks tmem/tcgen05 support in some main libraries, indicating partial feature-level gaps rather than a full contradiction of the toolchain-support claim. missing for 10: independent benchmark/library compatibility matrix confirming full CUDA feature parity across major frameworks.

   • [claimed-docs] “Optimized for NVIDIA CUDA-X™ libraries like RAPIDS, it supercharges GPU-accelerated analytics and AI tasks using APIs that mirror popular op…”
   • [claimed-docs] “The toolkit includes GPU-accelerated libraries, debugging and optimization tools, a C/C++ compiler, and a runtime library.”
   • [claimed-docs] “cuTile Python is an expression of the CUDA Tile programming model in Python. It is built on top of the CUDA Tile IR specification and allows…”
   • [community] “Converting four RTX PRO 6000 Blackwell cards to waterblocks, finding a VRM choke loose on the workbench, and getting back to 41k tok/s.”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the CUDA Toolkit page at developer.nvidia.com answered a keyless curl naming CUDA Toolkit — the compute…”

   proof ↗⚑ flag

Frameworks

1. ml engineerPyTorch and mainstream ML frameworks run on this GPU through officially documented builds and support matrices

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT✓fullclaimed8/10

   AMD's official ROCm docs explicitly list RX 9000 series support for PyTorch (Windows and Linux), TensorFlow, JAX, ONNX, vLLM, and Llama.cpp, with a documented support matrix and OS support (Windows/Linux) confirmed on AMD's product page. Missing for 10: independent hands-on confirmation of install success/version compatibility and no community corroboration of real-world PyTorch training/inference workflows on this specific card.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”

   proof ↗⚑ flag

   RTX PRO 6000 Blackwell!disputedcontradicted4/10

   NVIDIA's docs claim CUDA-X/CUDA toolkit compatibility and general AI/LLM workflows on the card, and community reports do show people running LLM inference workloads (41k tok/s) on RTX PRO 6000 Blackwell units, suggesting frameworks do run. However, a specific hands-on/community comment states these cards are SM120 architecture 'so no tmem/tcgen05 and lack of support in main libraries,' directly contradicting the notion of seamless official framework support via standard build/support matrices. Missing for 10: an explicit official PyTorch/framework support matrix or release notes confirming Blackwell SM120 compatibility, and resolution of the tcgen05/tmem library-support gap raised by users.

   • [claimed-docs] “Optimized for NVIDIA CUDA-X™ libraries like RAPIDS, it supercharges GPU-accelerated analytics and AI tasks using APIs that mirror popular op…”
   • [claimed-docs] “The toolkit includes GPU-accelerated libraries, debugging and optimization tools, a C/C++ compiler, and a runtime library.”
   • [community] “Converting four RTX PRO 6000 Blackwell cards to waterblocks, finding a VRM choke loose on the workbench, and getting back to 41k tok/s.”
   • [community] “Those are SM120 so no tmem/tcgen05 and lack of support in main libraries... For that money I'd buy a single B300, similar total AI TOPS, sim…”

   proof ↗⚑ flag