GeForce RTX 5090 vs RTX PRO 6000 Blackwell

Agent access

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

   weight 2 · round to RTX PRO 6000 Blackwell
   GeForce RTX 5090~partialprobed5/10

   NVIDIA's developer portal serves a valid llms.txt (HTTP 200, descriptive content) that an agent could use to discover CUDA/GPU-related docs, but this is at the general developer.nvidia.com domain rather than an RTX-5090-specific surface, and adjacent agent-friendly affordances (markdown doc exports, OpenAPI spec) are absent (404s). missing for 10: RTX-5090-specific llms.txt or agent doc entry point, working markdown/API exports, independent confirmation agents actually use this pathway successfully.

   • [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

   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 drawn
   GeForce RTX 5090—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 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
   GeForce RTX 5090—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 GeForce RTX 5090
   GeForce RTX 5090~partialprobed3/10

   CUDA Toolkit documentation describes a programmatic API (CUDA, cuTile Python/C++) for building GPU-accelerated applications, which is the closest analog to a 'documented public API' for this hardware product, but this is a low-level compute-kernel API, not an agent-drivable control interface, and direct probes found no OpenAPI/Swagger spec or machine-readable docs (404s). Missing for 10: a structured/machine-readable API spec (OpenAPI/REST), any agentic control surface, and independent corroboration of AI-native programmatic access beyond raw CUDA kernel programming.

   • [claimed-docs] “The NVIDIA® CUDA® Toolkit provides a development environment for creating high-performance, GPU-accelerated applications.”
   • [claimed-docs] “cuTile Python is an expression of the CUDA Tile programming model in Python.”
   • [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

   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 GeForce RTX 5090
   GeForce RTX 5090✓fullclaimed7/10

   NVIDIA provides official SDKs (CUDA Toolkit, CUDA Tile C++/cuTile Python, RTX Neural Shaders SDK, RTX Mega Geometry, Nsight tools) that developers can build AI/graphics applications against, all documented on NVIDIA's developer portal. Missing for 10: independent/hands-on developer corroboration of building against these SDKs, and deeper API reference/sample documentation beyond marketing-style descriptions.

   • [claimed-docs] “The NVIDIA® CUDA® Toolkit provides a development environment for creating high-performance, GPU-accelerated applications.”
   • [claimed-docs] “CUDA Tile C++ is an expression of the CUDA Tile programming model in C++. It's built on top of the CUDA Tile IR specification and allows you…”
   • [claimed-docs] “cuTile Python is an expression of the CUDA Tile programming model in Python.”
   • [claimed-docs] “The RTX Neural Shaders SDK lets developers train shader data on an RTX PRO workstation and accelerate neural representations with NVIDIA Ten…”
   • [claimed-docs] “RTX Mega Geometry dramatically increases the geometric detail possible in ray-traced scenes, accelerating BVH building to enable up to 100x …”
   • [claimed-docs] “NVIDIA Nsight Compute and Nsight System suite of tools designed to help developers optimize and increase performance of their applications.”

   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
   GeForce RTX 5090—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
   GeForce RTX 5090—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
   GeForce RTX 5090—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 GeForce RTX 5090
   GeForce RTX 5090~partialcommunity5/10

   NVIDIA's RTX documentation confirms fifth-gen Tensor Cores with FP4/FP8/FP6 low-precision support for deep learning workloads, and community discussion references RTX 5090 use for local LLM inference (though cost concerns are raised). However, there is no evidence of explicit support/documentation for named serving stacks like TensorRT-LLM, vLLM, or llama.cpp on this specific part. Missing for 10: documented compatibility with TensorRT-LLM, vLLM, or llama.cpp serving frameworks, benchmark data showing actual inference throughput on this GPU.

   • [claimed-docs] “Fifth-generation Tensor Cores deliver up to 3x higher throughput for deep learning, with new FP4 support for massive performance gains along…”
   • [community] “"If the prices for the RTX 5090 remain at 3500€, they will likely remain insignificant for the DIY crowd" for local LLM use compared to used…”
   • [claimed-docs] “The GeForce RTX 5090 is powered by the NVIDIA Blackwell architecture and equipped with 32 GB of super-fast GDDR7 memory, so you can do it al…”

   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 to GeForce RTX 5090
   GeForce RTX 5090~partialprobed3/10

   Docs mention fifth-gen Tensor Cores with specific precision support (FP4, TF32, BF16, FP16, FP8, FP6) and a relative claim of 'up to 3x higher throughput,' but no evidence gives an absolute TFLOPS/TOPS figure paired with sparsity state — the story explicitly wants a non-bare number with precision AND sparsity documented. Missing for 10: dense vs sparse TOPS/TFLOPS tables per precision, official spec-sheet numeric throughput figures, and independent benchmark corroboration of those numbers for ML workload sizing.

   • [claimed-docs] “Fifth-generation Tensor Cores deliver up to 3x higher throughput for deep learning, with new FP4 support for massive performance gains along…”
   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's RTX 5090 product/spec page answered a keyless curl and names the part — the vendor spec surfac…”

   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
   GeForce RTX 5090—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
   GeForce RTX 5090—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
   GeForce RTX 5090—none0/10

   The evidence pack covers CUDA, DLSS, RT Cores, and gaming features but contains no documentation of NVENC/AV1/HEVC hardware encoders, Studio Driver certification, or ISV-certified professional app support for the RTX 5090. Missing for 10: any mention of hardware encoder specs, Studio Driver program, or ISV certification for creator applications.

   ⚑ 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
   GeForce RTX 5090—none0/10

   The evidence pack contains no mention of NVLink, Infinity Fabric, multi-GPU interconnect, or rack-scale deployment for the RTX 5090; all specs describe a single consumer GPU (GDDR7, PCIe 5.0) and community commentary discusses it only as a DIY/local-LLM card, not datacenter-scale training/serving infrastructure.

   • [claimed-docs] “The GeForce RTX 5090 is powered by the NVIDIA Blackwell architecture and equipped with 32 GB of super-fast GDDR7 memory, so you can do it al…”
   • [community] “Pros: Fastest GPU around (usually), 32GB GDDR7 on 512-bit bus, PCIe 5.0, potent AI performance. Cons: Driver issues in some games/apps, extr…”
   • [community] “"If the prices for the RTX 5090 remain at 3500€, they will likely remain insignificant for the DIY crowd" for local LLM use compared to used…”

   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 GeForce RTX 5090
   GeForce RTX 5090~partialcommunity5/10

   Independent Phoronix benchmarking confirms the RTX 5090 is tested and functional on Linux across 60+ compute workloads, showing real-world Linux usability, but the evidence pack contains no first-party documentation of dedicated Linux driver releases, changelogs, or Linux-specific support pages from NVIDIA. Missing for 10: documented NVIDIA Linux driver release notes/changelog, official Linux support/compatibility docs, broader independent Linux gaming/compute test corroboration beyond one Phoronix reference.

   • [community] “Phoronix Linux benchmarks found the GeForce RTX 5090 delivering 1.42x the performance of the RTX 4090 across 60+ compute benchmarks, but on …”

   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 drawn
   GeForce RTX 5090—none0/10

   The evidence pack contains no mention of open-source kernel modules (e.g., NVIDIA's open GPU kernel module project) or upstream Linux driver support for the RTX 5090; all driver-related community mentions are about closed-driver bugs/issues, not open-source availability. This is a fair axis for a GPU (vendors like NVIDIA do ship open kernel modules), but nothing in the evidence documents it for this card.

   ⚑ 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 GeForce RTX 5090
   GeForce RTX 5090~partialcommunity6/10

   Independent Tom's Hardware and Phoronix benchmarks corroborate the RTX 5090 as the fastest consumer GPU (1.42x over 4090), supporting vendor claims of top-tier gaming performance, and NVIDIA's DLSS/Reflex/path-tracing feature docs target high-refresh 4K use cases. However, community evidence raises real caveats: reviewers flag Founders Edition thermal issues, similar-or-worse perf-per-watt vs 4080/4090, and specifically critique Multi Frame Generation as 'marketing' since input sampling doesn't scale with the reported FPS boost, undercutting the headline frame-rate claims. missing for 10: dedicated 4K high-refresh benchmark suites (e.g. specific FPS-at-4K numbers across many AAA titles), resolution of the MFG input-latency criticism, and confirmation thermal/efficiency issues don't limit sustained high-refresh performance.

   • [claimed-docs] “Powered by GeForce RTX 50 Series and fifth-generation Tensor Cores, new DLSS Multi Frame Generation boosts FPS by using AI to generate up to…”
   • [claimed-docs] “Reflex technologies optimize the graphics pipeline for ultimate responsiveness, providing faster target acquisition, quicker reaction times,…”
   • [claimed-docs] “The NVIDIA Blackwell architecture unlocks the game-changing realism of path tracing. Experience cinematic quality visuals at unprecedented s…”
   • [community] “Pros: Fastest GPU around (usually), 32GB GDDR7 on 512-bit bus, PCIe 5.0, potent AI performance. Cons: Driver issues in some games/apps, extr…”
   • [community] “We've now docked half a star, due to concerns specifically with the Founders Edition running hot.”
   • [community] “MFG as an example running at 240 FPS would mean user input only gets sampled at 60 FPS. That's not the same as a game running at 240 FPS nat…”
   • [community] “Phoronix Linux benchmarks found the GeForce RTX 5090 delivering 1.42x the performance of the RTX 4090 across 60+ compute benchmarks, but on …”

   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 GeForce RTX 5090
   GeForce RTX 5090✓fullcommunity9/10

   NVIDIA's official docs detail DLSS 4 with Multi Frame Generation, Super Resolution, Ray Reconstruction, and DLAA on RTX 5090/50-series, plus broad game rollout via the NVIDIA app supporting hundreds of titles. Independent review (Tom's Hardware) confirms these features work in practice, though it flags marketing caveats around Multi Frame Generation's input latency implications. Missing for 10: independent per-game compatibility list/count and more third-party benchmarking corroboration beyond one review.

   • [claimed-docs] “Powered by GeForce RTX 50 Series and fifth-generation Tensor Cores, new DLSS Multi Frame Generation boosts FPS by using AI to generate up to…”
   • [claimed-docs] “Dynamically adjust your multiplier to maximize smoothness across different games and scenes on GeForce RTX 50 Series GPUs.”
   • [claimed-docs] “Enhances image quality by using AI to generate additional pixels for intensive ray-traced scenes.”
   • [claimed-docs] “Boosts performance by using AI to output higher-resolution frames from a lower-resolution input.”
   • [claimed-docs] “Provides higher image quality with an AI-based anti-aliasing technique. DLAA uses the same Super Resolution technology developed for DLSS, c…”
   • [claimed-docs] “With the NVIDIA app you can update hundreds of games to use the latest DLSS features including Multi Frame Generation, and the newest AI mod…”
   • [community] “Pros: Fastest GPU around (usually), 32GB GDDR7 on 512-bit bus, PCIe 5.0, potent AI performance. Cons: Driver issues in some games/apps, extr…”
   • [community] “MFG as an example running at 240 FPS would mean user input only gets sampled at 60 FPS. That's not the same as a game running at 240 FPS nat…”

   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
   GeForce RTX 5090~partialcommunity6/10

   NVIDIA publishes the RTX 5090's 32GB GDDR7 VRAM (docs-18) and strong Tensor Core throughput (docs-22), which is enough for some 70B-class models at aggressive quantization, but the evidence never states a specific memory-bandwidth figure and community discussion (comm-5) notes the GPU's price makes it 'insignificant for the DIY crowd' compared to used 3090s or Mac unified memory for local LLM work, undercutting the 'practical' framing. Missing for 10: published memory-bandwidth spec (GB/s), explicit vendor guidance on running 70B-class quantized models, and independent benchmarks confirming inference throughput at that scale.

   • [claimed-docs] “The GeForce RTX 5090 is powered by the NVIDIA Blackwell architecture and equipped with 32 GB of super-fast GDDR7 memory, so you can do it al…”
   • [claimed-docs] “Fifth-generation Tensor Cores deliver up to 3x higher throughput for deep learning, with new FP4 support for massive performance gains along…”
   • [community] “"If the prices for the RTX 5090 remain at 3500€, they will likely remain insignificant for the DIY crowd" for local LLM use compared to used…”

   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 GeForce RTX 5090
   GeForce RTX 5090~partialprobed7/10

   NVIDIA's own product page confirms capacity (32GB) and memory type (GDDR7), and community review corroborates a 512-bit bus, but no evidence pack item states the exact memory bandwidth figure (GB/s) for this part. Missing for 10: an explicit published bandwidth number (GB/s) from a first-party spec sheet.

   • [claimed-docs] “The GeForce RTX 5090 is powered by the NVIDIA Blackwell architecture and equipped with 32 GB of super-fast GDDR7 memory, so you can do it al…”
   • [community] “Pros: Fastest GPU around (usually), 32GB GDDR7 on 512-bit bus, PCIe 5.0, potent AI performance. Cons: Driver issues in some games/apps, extr…”
   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's RTX 5090 product/spec page answered a keyless curl and names the part — the vendor spec surfac…”

   proof ↗⚑ 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 drawn
   GeForce RTX 5090—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 userSelf-host the core product

   weight 3 · round to RTX PRO 6000 Blackwell
   GeForce RTX 5090—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✓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 to GeForce RTX 5090
   GeForce RTX 5090!disputedcontradicted5/10

   NVIDIA's spec page exposes board power/TOPS figures (probe-rt-1) but no explicit efficiency/perf-per-watt marketing claim is cited; independent testing (Phoronix via HN, comm-6/7/8) directly contradicts any efficiency narrative, finding RTX 5090 perf-per-watt is similar to or worse than the 4080/4090 despite higher absolute performance, and Tom's Hardware also flags thermal/power concerns (comm-2). Missing for 10: a documented power-envelope/TDP spec sheet from NVIDIA explicitly framed for ML workloads, and independent perf-per-watt benchmarks that confirm rather than undercut efficiency gains.

   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's RTX 5090 product/spec page answered a keyless curl and names the part — the vendor spec surfac…”
   • [community] “TL;DR; performance isn't bad, but perf per Watt isn't better than 4080 or 4090 and can even be significantly lower than 4090 in certain cont…”
   • [community] “"the 4080 Super doing well compared to the 5080 and 5090... seems to have better performance per watt ratio than them while also having some…”
   • [community] “Phoronix Linux benchmarks found the GeForce RTX 5090 delivering 1.42x the performance of the RTX 4090 across 60+ compute benchmarks, but on …”
   • [community] “We've now docked half a star, due to concerns specifically with the Founders Edition running hot.”

   proof ↗⚑ 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 to GeForce RTX 5090
   GeForce RTX 5090!disputedcontradicted4/10

   Evidence confirms NVIDIA's official 5090 page exposes board-power and spec data (probe-rt-1) and the community references the 12VHPWR/12V-2x6 connector spec, but no evidence pack item actually cites the published TDP/TGP wattage, PSU wattage recommendation, or explicit cooling/case guidance for this exact card. More importantly, community evidence (comm-4) documents real-world 12VHPWR connector melting incidents tied to the card's power-connector design, and comm-2 reports the Founders Edition running hot — concretely undermining confidence that a build spec'd purely around the vendor's connector/cooling guidance will be reliable. missing for 10: explicit first-party TDP/TGP wattage figure, official PSU/connector spec sheet, first-party cooling/case airflow guidance, resolution of the connector-melting safety concern.

   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's RTX 5090 product/spec page answered a keyless curl and names the part — the vendor spec surfac…”
   • [community] “Discussion centers on a reported RTX 5090 FE 12VHPWR connector melting; users debate that the FE's single 12V bus-bar design relies purely o…”
   • [community] “We've now docked half a star, due to concerns specifically with the Founders Edition running hot.”
   • [claimed-docs] “The GeForce RTX 5090 is powered by the NVIDIA Blackwell architecture and equipped with 32 GB of super-fast GDDR7 memory, so you can do it al…”

   proof ↗⚑ 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
   GeForce RTX 5090—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
   GeForce RTX 5090✓fullcommunity8/10

   NVIDIA's CUDA Toolkit docs explicitly target GeForce RTX GPUs including Blackwell-architecture cards like the 5090, and independent Phoronix benchmarks (cited via comm-8) confirm real compute workloads running on the 5090 with 1.42x uplift over the 4090 across 60+ compute benchmarks, corroborating that it functions as a genuine CUDA compute target. Missing for 10: no explicit CUDA compute-capability/SM version listing naming '5090' directly in vendor docs, and no independent report specifically validating professional GPU-compute (non-gaming) toolchains beyond Phoronix's Linux compute suite.

   • [claimed-docs] “The NVIDIA® CUDA® Toolkit provides a development environment for creating high-performance, GPU-accelerated applications.”
   • [claimed-docs] “CUDA Tile C++ is an expression of the CUDA Tile programming model in C++. It's built on top of the CUDA Tile IR specification and allows you…”
   • [claimed-docs] “cuTile Python is an expression of the CUDA Tile programming model in Python.”
   • [claimed-docs] “Fifth-generation Tensor Cores deliver up to 3x higher throughput for deep learning, with new FP4 support for massive performance gains along…”
   • [community] “Phoronix Linux benchmarks found the GeForce RTX 5090 delivering 1.42x the performance of the RTX 4090 across 60+ compute benchmarks, but on …”

   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 GeForce RTX 5090
   GeForce RTX 5090~partialcommunity3/10

   Evidence confirms NVIDIA ships a general CUDA Toolkit and Tensor Core architecture details relevant to deep learning, but there is no explicit official PyTorch/TensorFlow support matrix, compute-capability listing, or documented install path referencing RTX 5090/Blackwell specifically; a community post even flags 5090 as impractical for local LLM work due to price, not toolchain issues. missing for 10: explicit PyTorch build/support-matrix docs naming RTX 5090 or Blackwell (sm_120) compute capability, cuDNN/cuBLAS version compatibility notes, and independent confirmation of PyTorch working out-of-the-box on the card.

   • [claimed-docs] “The NVIDIA® CUDA® Toolkit provides a development environment for creating high-performance, GPU-accelerated applications.”
   • [claimed-docs] “Fifth-generation Tensor Cores deliver up to 3x higher throughput for deep learning, with new FP4 support for massive performance gains along…”
   • [community] “"If the prices for the RTX 5090 remain at 3500€, they will likely remain insignificant for the DIY crowd" for local LLM use compared to used…”

   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