In this article
The original RTX 5090 D has 32 GB; its old page redirects to D v2, so the historical specification needs its own evidence.
Establish the original model
NVIDIA’s official announcement for the original RTX 5090 D describes 32 GB GDDR7. Its former product URL now redirects to the RTX 5090 D v2 page, which has a different capacity. Source identity and date are therefore part of technical validation rather than editorial tidiness alone. The table concerns the original card and memory per GPU. Reliable board power is not established by the historical source used here; do not substitute a global RTX 5090 or D v2 value. Likewise, a regional D suffix does not establish inference backend restrictions without separately verified documentation.
| Official variant | Memory per GPU | Memory type | Board power | Evidence |
|---|---|---|---|---|
| NVIDIA GeForce RTX 5090 D — Original China RTX 5090 D 32 GB | 32 GB | GDDR7 | Not verified | Specification |
Validate the actual LLM stack
The RTX 5090 D belongs to Blackwell, but server acceptance depends on the working stack. vLLM specifies a CC 7.5 hardware minimum and additional environment requirements. This is not certification for every regional board, dtype or quantization. The manifest records actual device identity, driver, engine version, checkpoint and selected kernels. Test a short response before the specified context and concurrency. On failure, distinguish unsupported operations from memory pressure. Having 32 GB does not establish token speed or a particular large model fit; CPU offload and KV cache allocation must remain visible rather than hidden behind a successful HTTP status.
Confirm the rendering path
The Blender Cycles manual describes CUDA, OptiX, driver requirements and RTX hardware acceleration. Run a saved scene on the original 5090 D through the selected backend and verify device detection in logs. Record project preparation, memory and image separately. Unknown specified board power does not prevent reading available telemetry, but an observed value must not become an official board limit. A successful Cycles job concerns one release and scene. It does not guarantee another renderer’s support or equality with the global RTX 5090 across every computational workload and application setting.
Maintain an inventory without identity substitution
The server inventory retains the original name, PCI identity, available VBIOS information and the AIB model established through documentation or physical identification. Compare these fields before jobs after an update. If telemetry starts returning another alias, investigate instead of automatically changing catalog capacity. Assess power and cooling using the actual board and manufacturer documentation. Similar regional labels do not justify borrowing another model’s power budget. LLM and render queues receive the resource after confirming memory ownership and previous work completion, rather than merely finding a familiar nvidia-smi name.
Preserve historical specification evidence
The verification package contains the announcement link, inventory snapshot and LLM and scene acceptance results. If the 32 GB inventory conflicts with observed capacity, stop interpreting workload results and investigate identity first: the source, record or actual device may differ. Renaming unknown hardware without evidence does not resolve the discrepancy. Once identity agrees, define permitted workloads and limitations. This profile is not a conclusion about legal status, purchase availability, special compute caps or completed external platform integration. It supports assessing the original RTX 5090 D against a verified historical specification instead of silently importing a replacement model’s data.
RTX 4090 vs RTX 5090 for LLMs: Compare 24GB and 32GB · Build a GPU Inventory CSV with nvidia-smi · GPU catalog