GeForce RTX 5090 vs NVIDIA H200 (SXM)

Agent access

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

   weight 2 · round drawn
   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

   NVIDIA H200 (SXM)~partialprobed5/10

   A probe confirms developer.nvidia.com/llms.txt returns HTTP 200 with a real summary, showing NVIDIA does expose an agent-readable entry point for its developer docs, but this is a generic portal file, not specific to H200 GPU documentation, and other agent-friendly formats (docs.md, OpenAPI) return 404s. Missing for 10: H200-specific machine-readable docs, working docs.md/OpenAPI endpoints, and confirmation an agent can navigate beyond the root llms.txt.

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

   NVIDIA H200 (SXM)—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 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

   NVIDIA H200 (SXM)—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

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

   NVIDIA H200 (SXM)—none0/10

   The H200 is a hardware accelerator; while CUDA Toolkit and Nsight tools provide programming interfaces, there is no evidence of a documented public REST/agentic API for driving the product, and explicit probes for OpenAPI/swagger specs all returned 404s.

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

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

   NVIDIA H200 (SXM)~partialprobed5/10

   NVIDIA provides official SDKs to build against (CUDA Toolkit, Nsight developer tools, and NIM microservices bundled via NVIDIA AI Enterprise) that target the H200 hardware, and a developer portal exists with an llms.txt discovery file. However, probes show no machine-readable docs (404 on .md) and no OpenAPI/swagger spec, and there's no H200-specific agentic SDK evidence beyond generic CUDA/NIM tooling. missing for 10: agent-specific SDK examples, machine-readable API docs (docs-md returned 404), OpenAPI spec availability, independent developer corroboration of SDK usability for AI-native/agentic workflows.

   • [claimed-docs] “NVIDIA AI Enterprise includes NVIDIA NIM™, a set of easy-to-use microservices designed to speed up enterprise generative AI deployment.”
   • [claimed-docs] “With it, you can develop, optimize, and deploy your applications on GPU-accelerated embedded systems, desktop workstations, enterprise data …”
   • [claimed-docs] “NVIDIA Nsight Compute and Nsight System suite of tools designed to help developers optimize and increase performance of their applications.”
   • [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

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

   NVIDIA H200 (SXM)—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

   NVIDIA H200 (SXM)—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

   NVIDIA H200 (SXM)—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

Api quality

1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   GeForce RTX 5090—none0/10

   This is a consumer GPU product; while NVIDIA's developer portal exists, an explicit probe found no OpenAPI/machine-readable API spec (all candidate paths 404), so there's no evidence of a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.nvidia.com/openapi.json, https://developer.nvidia.com/swagger.json, https://develo…”

   proof ↗⚑ flag

   NVIDIA H200 (SXM)—none0/10

   The H200 is a hardware GPU; NVIDIA's developer portal was probed for machine-readable API specs (openapi.json, swagger.json, etc.) and all returned 404, showing no discoverable OpenAPI spec is published.

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

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

   NVIDIA H200 (SXM)~partialprobed4/10

   NVIDIA docs and runtime probes confirm H200's HBM3e specs and FP8 tensor performance figures, and community evidence shows real-world LLM inference (Llama2, Llama 405B) throughput gains, but no evidence names FP4 support or specific serving-stack integration (TensorRT-LLM, vLLM, ROCm, llama.cpp) for this part. missing for 10: explicit FP4 precision docs, named serving-stack support (TensorRT-LLM/vLLM/ROCm/llama.cpp) tied to H200.

   • [claimed-docs] “The H200 boosts inference speed by up to 2X compared to H100 GPUs when handling LLMs like Llama2.”
   • [claimed-docs] “the NVIDIA H200 is the first GPU to offer 141 gigabytes (GB) of HBM3e memory at 4.8 terabytes per second (TB/s)”
   • [community] “Llama 405B up to 142 tok/s on Nvidia H200 SXM — launched a production grade API endpoint at $3 per million tokens, made possible by H200 SXM…”
   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's H200 datacenter page answered a keyless curl and names the part — the spec table (141GB HBM3e,…”

   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 NVIDIA H200 (SXM)
   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

   NVIDIA H200 (SXM)~partialprobed4/10

   NVIDIA's H200 page is confirmed live and does contain a spec table with FP8 tensor figures and bandwidth/capacity numbers (per probe-rt-1), but the evidence pack itself surfaces mostly bare marketing multipliers ('2X faster than H100', '110X faster than CPU') rather than the actual precision-tagged TFLOPS/TOPS figures with sparsity conditions spelled out. Community commentary also notes the H200 reuses H100 silicon, adding skepticism to headline comparisons rather than to the raw spec numbers themselves. Missing for 10: explicit quoted TFLOPS/TOPS values per precision (FP8/FP16/INT8) with dense vs. sparse figures, and independent benchmark corroboration of those specific numbers.

   • [claimed-docs] “The H200 boosts inference speed by up to 2X compared to H100 GPUs when handling LLMs like Llama2.”
   • [claimed-docs] “the NVIDIA H200 is the first GPU to offer 141 gigabytes (GB) of HBM3e memory at 4.8 terabytes per second (TB/s)”
   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's H200 datacenter page answered a keyless curl and names the part — the spec table (141GB HBM3e,…”
   • [community] “The H200 GPU die is the same as the H100, but it's using a full set of faster 24GB memory stacks... This is an H100 141GB, not new silicon l…”

   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

   NVIDIA H200 (SXM)—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

   NVIDIA H200 (SXM)—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 drawn
   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

   NVIDIA H200 (SXM)—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

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 to NVIDIA H200 (SXM)
   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

   NVIDIA H200 (SXM)~partialcommunity6/10

   Evidence confirms the SXM form factor, MIG partitioning, CUDA toolkit for datacenter deployment, and community proof of real multi-GPU serving (Llama 405B at 142 tok/s across H200 SXMs) validating datacenter-scale operation, but the pack never cites NVLink/NVSwitch bandwidth figures, Infinity Fabric, or DGX/HGX rack-scale system specs that the story explicitly asks for. missing for 10: explicit NVLink/NVSwitch bandwidth numbers, DGX/HGX rack-scale system documentation, independent rack-scale benchmark corroboration.

   • [claimed-docs] “the NVIDIA H200 is the first GPU to offer 141 gigabytes (GB) of HBM3e memory at 4.8 terabytes per second (TB/s)”
   • [claimed-docs] “Multi-Instance GPUs Up to 7 MIGs @18GB each”
   • [community] “Llama 405B up to 142 tok/s on Nvidia H200 SXM — launched a production grade API endpoint at $3 per million tokens, made possible by H200 SXM…”
   • [claimed-docs] “With it, you can develop, optimize, and deploy your applications on GPU-accelerated embedded systems, desktop workstations, enterprise data …”

   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

   NVIDIA H200 (SXM)—none0/10

   Evidence pack lacks any explicit mention of Linux driver releases, release notes, or independent Linux benchmarking/testing of the H200; CUDA toolkit blurb only vaguely references 'data centers' and 'supercomputers' without naming Linux, and community links focus on inference throughput or die comparisons, not OS-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

   NVIDIA H200 (SXM)—none0/10

   Evidence shows only proprietary CUDA toolkit and NVIDIA AI Enterprise stack; nothing about open-source kernel modules (nvidia-open) or upstream Linux driver support is documented in the pack. Missing for 10: any mention of NVIDIA's open GPU kernel modules, upstream mainline Linux driver support, or open-source driver documentation for the H200.

   • [claimed-docs] “With it, you can develop, optimize, and deploy your applications on GPU-accelerated embedded systems, desktop workstations, enterprise data …”
   • [claimed-docs] “NVIDIA Nsight Compute and Nsight System suite of tools designed to help developers optimize and increase performance of their applications.”

   proof ↗⚑ 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

   NVIDIA H200 (SXM)—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

   NVIDIA H200 (SXM)—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

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 NVIDIA H200 (SXM)
   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

   NVIDIA H200 (SXM)✓fullprobed9/10

   NVIDIA docs confirm 141GB HBM3e at 4.8TB/s, comfortably fitting a 70B-class quantized model with large batch/context headroom, and this is corroborated by an independent runtime probe and community benchmarks showing real-world inference (e.g., Llama 405B at 142 tok/s) on H200 SXM. Missing for 10: independent hands-on benchmark specifically for a 70B-class quantized model rather than larger models.

   • [claimed-docs] “the NVIDIA H200 is the first GPU to offer 141 gigabytes (GB) of HBM3e memory at 4.8 terabytes per second (TB/s)”
   • [community] “Llama 405B up to 142 tok/s on Nvidia H200 SXM — launched a production grade API endpoint at $3 per million tokens, made possible by H200 SXM…”
   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's H200 datacenter page answered a keyless curl and names the part — the spec table (141GB HBM3e,…”

   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

   NVIDIA H200 (SXM)~partialprobed6/10

   NVIDIA's official H200 page publishes capacity (141GB), memory type (HBM3e), and bandwidth (4.8TB/s), and a runtime probe confirms this spec table is live and fetchable; independent commentary also confirms it's HBM3e stacks on the H100 die. However, memory bus width is never stated anywhere in the evidence pack. Missing for 10: explicit memory bus-width figure, and any independent/third-party spec-sheet corroboration beyond NVIDIA's own page.

   • [claimed-docs] “the NVIDIA H200 is the first GPU to offer 141 gigabytes (GB) of HBM3e memory at 4.8 terabytes per second (TB/s)”
   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's H200 datacenter page answered a keyless curl and names the part — the spec table (141GB HBM3e,…”
   • [community] “The H200 GPU die is the same as the H100, but it's using a full set of faster 24GB memory stacks... This is an H100 141GB, not new silicon l…”

   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

   NVIDIA H200 (SXM)—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 NVIDIA H200 (SXM)
   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

   NVIDIA H200 (SXM)✓fullcommunity7/10

   The H200 is physical hardware you purchase/own and deploy in your own datacenter or colo, making self-hosting the core product inherently possible (unlike SaaS AI products), and NVIDIA's stack (CUDA toolkit, drivers, Nsight tools) supports fully on-prem deployment across data centers and workstations. missing for 10: no direct documentation of an on-prem purchase/procurement path or hands-on self-hosting case study, and no independent report confirming ease of self-managed deployment outside of cloud providers.

   • [claimed-docs] “With it, you can develop, optimize, and deploy your applications on GPU-accelerated embedded systems, desktop workstations, enterprise data …”
   • [claimed-docs] “NVIDIA Nsight Compute and Nsight System suite of tools designed to help developers optimize and increase performance of their applications.”
   • [claimed-docs] “the NVIDIA H200 is the first GPU to offer 141 gigabytes (GB) of HBM3e memory at 4.8 terabytes per second (TB/s)”
   • [community] “Llama 405B up to 142 tok/s on Nvidia H200 SXM — launched a production grade API endpoint at $3 per million tokens, made possible by H200 SXM…”

   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 NVIDIA H200 (SXM)
   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

   NVIDIA H200 (SXM)~partialcommunity3/10

   NVIDIA's own docs state the H200 operates 'within the same power profile as the H100' (nvidia-h200-sxm-docs-4), but this is a vendor claim only — no independent performance-per-watt benchmarks or third-party power-envelope testing are present in the evidence pack. Community notes (nvidia-h200-sxm-comm-2) even highlight that H200 shares H100 silicon, which is consistent but not an efficiency benchmark. Missing for 10: independent/hands-on power-draw measurements under sustained load, third-party perf/watt comparisons, and detailed thermal/power documentation beyond the single marketing sentence.

   • [claimed-docs] “This cutting-edge technology offers unparalleled performance, all within the same power profile as the H100.”
   • [community] “The H200 GPU die is the same as the H100, but it's using a full set of faster 24GB memory stacks... This is an H100 141GB, not new silicon l…”

   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

   NVIDIA H200 (SXM)—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

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

   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

   NVIDIA H200 (SXM)—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

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

   NVIDIA H200 (SXM)✓fullprobed8/10

   CUDA Toolkit is NVIDIA's standard GPU-compute toolchain, explicitly documented as supporting deployment across data centers and supercomputers, and H200 is the current flagship data-center GPU in this same product family/lineage; community evidence (production LLM inference deployments on H200 SXM) confirms real-world CUDA-based workloads running on this part. Missing for 10: no explicit CUDA compute-capability/architecture list page directly naming 'H200' as a supported gpu-architecture target string, and no ROCm angle (not applicable to NVIDIA anyway).

   • [claimed-docs] “With it, you can develop, optimize, and deploy your applications on GPU-accelerated embedded systems, desktop workstations, enterprise data …”
   • [claimed-docs] “NVIDIA Nsight Compute and Nsight System suite of tools designed to help developers optimize and increase performance of their applications.”
   • [community] “Llama 405B up to 142 tok/s on Nvidia H200 SXM — launched a production grade API endpoint at $3 per million tokens, made possible by H200 SXM…”
   • [probe] “PROBE runtime (recorded 2026-09-15): NVIDIA's H200 datacenter page answered a keyless curl and names the part — the spec table (141GB HBM3e,…”

   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 NVIDIA H200 (SXM)
   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

   NVIDIA H200 (SXM)~partialcommunity6/10

   NVIDIA documents CUDA Toolkit support for developing/deploying GPU-accelerated applications and community evidence (HN inference benchmark) shows PyTorch-based LLM workloads (Llama 405B) running in production on H200 SXM, implying framework compatibility via CUDA. However, there is no direct citation of an official PyTorch/TensorFlow support matrix or explicit framework-version compatibility documentation for H200 specifically. Missing for 10: explicit PyTorch/TensorFlow official support matrix naming H200, CUDA/cuDNN version compatibility table, first-party framework installation guide referencing H200.

   • [claimed-docs] “With it, you can develop, optimize, and deploy your applications on GPU-accelerated embedded systems, desktop workstations, enterprise data …”
   • [claimed-docs] “NVIDIA Nsight Compute and Nsight System suite of tools designed to help developers optimize and increase performance of their applications.”
   • [community] “Llama 405B up to 142 tok/s on Nvidia H200 SXM — launched a production grade API endpoint at $3 per million tokens, made possible by H200 SXM…”

   proof ↗⚑ flag