AMD Instinct MI355X vs NVIDIA GeForce RTX 5080 Mobile Comparison

Head-to-Head Benchmarks

The database contains no direct head-to-head benchmark comparisons between the AMD Instinct MI355X and the NVIDIA GeForce RTX 5080 Mobile. The head-to-head benchmark array is empty, and the win counts for both parts sit at zero. This absence of overlapping test data is itself informative. The Instinct MI355X has no recorded benchmark scores at all; its average benchmark score is 0, and its percentile rank against all GPUs is 50. The RTX 5080 Mobile, by contrast, carries a full suite of ten recorded tests, an average benchmark score of 38,349, and a percentile rank of 81.

The RTX 5080 Mobile's recorded results show a wide spread across test types. In 3DMark Steel Nomad DX12, it scores 4,952. Its Geekbench OpenCL result is 166,986, and its Geekbench Vulkan score is 169,754. Passmark results range from a low of 116 in DirectX 12 to a high of 314 in DirectX 9, with DirectX 10 at 171 and DirectX 11 at 253. The Passmark G2D score is 1,095, while the G3D score reaches 27,711. The GPU compute result sits at 12,134.

The nearest rival data for the RTX 5080 Mobile shows how tightly clustered its competition is. The NVIDIA GeForce MX570 scores 38,299, which is 0.1% behind the RTX 5080 Mobile. The NVIDIA GeForce RTX 4080 Mobile scores 38,135, a 0.6% deficit. On the other side, the NVIDIA GeForce MX570 A scores 38,691, which is 0.9% ahead, and the AMD Radeon Pro 580X scores 38,706, also 0.9% ahead. The RTX 5080 Mobile sits in a narrow band where a 1% swing either way changes its standing among immediate rivals.

What the data cannot show is a direct comparison of compute throughput between the two cards, because the MI355X has no benchmark entries. The raw specification fields differ so greatly that a head-to-head test would likely be dominated by the MI355X in raw compute, but no recorded measurements confirm this. The MI355X's FP32 throughput is listed as 78.64 TFLOPS, while the RTX 5080 Mobile is listed at 23.04 TFLOPS. Texture rate for the MI355X is 2,457.6 GTexel/s versus 360.0 GTexel/s for the NVIDIA part. Pixel rate is another stark separator: the MI355X is listed at 0 MPixel/s, while the RTX 5080 Mobile delivers 144.0 GPixel/s.

The percentile data reinforces the positioning. The RTX 5080 Mobile at percentile 81 places it above the majority of all GPUs in the database. The MI355X at percentile 50 lands exactly at the median, but this figure is derived from zero recorded benchmark scores, so it should be interpreted as a placeholder rather than a measured result.

FAQ

Q: Does the AMD Instinct MI355X have any recorded benchmark scores in the database?

A: No. The MI355X has an empty benchmarks array, an average benchmark score of 0, and no nearest rivals listed. The RTX 5080 Mobile, in contrast, has ten recorded tests spanning 3DMark, Geekbench, and Passmark suites.

Q: How does the RTX 5080 Mobile compare to its closest rivals in average benchmark score?

A: The RTX 5080 Mobile averages 38,349. The GeForce MX570 trails by 0.1% at 38,299, and the GeForce RTX 4080 Mobile trails by 0.6% at 38,135. The MX570 A leads by 0.9% at 38,691, and the Radeon Pro 580X leads by 0.9% at 38,706.

Q: What is the FP32 compute difference between the two cards?

A: The MI355X is listed at 78.64 TFLOPS FP32, while the RTX 5080 Mobile is listed at 23.04 TFLOPS FP32. Both cards also list FP16 at a 1:1 ratio with their respective FP32 figures.

Q: Which card has the higher memory bandwidth?

A: The MI355X lists 8.19 TB/s of bandwidth from 288 GB of HBM3e memory on an 8192-bit bus. The RTX 5080 Mobile lists 896.0 GB/s from 16 GB of GDDR7 memory on a 256-bit bus.

Q: Are there any direct head-to-head benchmark results between these two cards?

A: No. The head-to-head benchmarks array is empty, and the win counts for both cards are zero. Any comparison must rely on the separate specification fields and the RTX 5080 Mobile's individual test scores.

Q: What API support does each card offer?

A: The MI355X lists N/A for DirectX, OpenGL, and Vulkan. The RTX 5080 Mobile lists DirectX 12 Ultimate (12_2), OpenGL 4.6, and Vulkan 1.4.

Where Each One Wins

The RTX 5080 Mobile wins in every category where recorded measurements exist, simply because the MI355X has no benchmark entries. The NVIDIA card has ten published test scores, a percentile rank of 81, and an average score of 38,349. It also has a nearest-rival profile that places it within 1% of four other GPUs, indicating strong competition at its performance tier.

The MI355X wins on raw specification sheets. Its FP32 throughput of 78.64 TFLOPS is more than triple the RTX 5080 Mobile's 23.04 TFLOPS. Its texture rate of 2,457.6 GTexel/s is nearly seven times the NVIDIA card's 360.0 GTexel/s. Memory capacity and bandwidth are not close: 288 GB versus 16 GB, and 8.19 TB/s versus 896.0 GB/s. The MI355X also carries 16,384 shading units against 7,680, and 1,024 TMUs against 240.

The RTX 5080 Mobile counters with features the MI355X lacks entirely. It has 96 ROPs and a pixel rate of 144.0 GPixel/s, while the MI355X lists 0 ROPs and 0 MPixel/s. The NVIDIA card has 60 RT cores and 240 tensor cores; the MI355X lists null for both. The RTX 5080 Mobile supports DirectX 12 Ultimate, OpenGL 4.6, and Vulkan 1.4, while the MI355X lists N/A for all three APIs. Display outputs on the RTX 5080 Mobile are described as portable device dependent, while the MI355X has no outputs at all.

A use-case split follows from these fields. The MI355X is positioned for compute workloads that demand massive memory capacity, extreme bandwidth, and high FP32 throughput, with no display or rendering expectations. The RTX 5080 Mobile is positioned for graphics rendering and general GPU workloads where rasterization, ray tracing, and API compatibility matter, all within a mobile power envelope.

Specification Differences

The process nodes differ: the MI355X uses a 3 nm process, while the RTX 5080 Mobile uses a 5 nm process, both from TSMC. Transistor counts are far apart, with the MI355X at 185,000 million transistors on a 2380 mm² die, giving a density of 77.7M per mm². The RTX 5080 Mobile has 45,600 million transistors on a 378 mm² die, yielding a higher density of 120.6M per mm². The MI355X has the larger chip, but the RTX 5080 Mobile packs transistors more tightly.

Clock speeds show a mixed picture. The MI355X has a base clock of 1000 MHz and a boost of 2400 MHz. The RTX 5080 Mobile has a base of 975 MHz and a boost of 1500 MHz. Memory clocks also differ: the MI355X runs at 2000 MHz with 8 Gbps effective, while the RTX 5080 Mobile runs at 1750 MHz with 28 Gbps effective.

Memory subsystems are entirely different classes. The MI355X uses 288 GB of HBM3e on an 8192-bit bus with 8.19 TB/s bandwidth. The RTX 5080 Mobile uses 16 GB of GDDR7 on a 256-bit bus with 896.0 GB/s bandwidth. The MI355X has 16,384 shading units, 1,024 TMUs, and 0 ROPs. The RTX 5080 Mobile has 7,680 shading units, 240 TMUs, and 96 ROPs. The RTX 5080 Mobile has 60 RT cores and 240 tensor cores; the MI355X lists null for both fields.

Power and physical specifications diverge sharply. The MI355X has a TDP of 1400 W, requires an 1800 W suggested PSU, and occupies an OAM Module slot. The RTX 5080 Mobile has a TDP of 80 W, lists no suggested PSU, and is an IGP form factor. Both use PCIe 5.0 x16 and have no power connectors listed. The MI355X dimensions are 102 mm by 165 mm, while the RTX 5080 Mobile has no dimensions recorded.

Release dates are close: the MI355X launched on 2025-06-11, and the RTX 5080 Mobile launched on 2025-04-01. The MI355X has no production status listed, while the RTX 5080 Mobile is marked Active. Neither card has a launch MSRP field populated. The MI355X's predecessor is Radeon Instinct, and the RTX 5080 Mobile's predecessor is GeForce 40 Mobile.

Architecture Differences

The MI355X uses the CDNA 4.0 architecture on the MI350 256CU chip, built for the Instinct (MIx) generation. The RTX 5080 Mobile uses the Blackwell 2.0 architecture on the GB203 chip, part of the GeForce 50-series and the GeForce 50 Mobile generation. These are fundamentally different design philosophies: CDNA 4.0 targets compute accelerators, while Blackwell 2.0 targets consumer and mobile graphics.

The MI355X's compute-first design is reflected in its zero ROP count and zero pixel rate. It has no display outputs and no graphics API support. Its 16,384 shading units and 1,024 TMUs feed a compute pipeline aimed at throughput, evidenced by the 78.64 TFLOPS FP32 figure and the 2,457.6 GTexel/s texture rate. The lack of RT cores and tensor cores in the listing suggests these fields are either not applicable or not disclosed for this accelerator class.

The RTX 5080 Mobile's Blackwell 2.0 design includes rasterization hardware in the form of 96 ROPs and a 144.0 GPixel/s pixel rate. It also includes 60 RT cores for ray tracing and 240 tensor cores for AI workloads. Its API support spans DirectX 12 Ultimate, OpenGL 4.6, and Vulkan 1.4, making it compatible with standard graphics software stacks. The portable device dependent display outputs indicate integration into laptops and mobile systems.

Transistor density tells a story about design priorities. The RTX 5080 Mobile achieves 120.6M transistors per mm², considerably denser than the MI355X's 77.7M per mm². The MI355X compensates with a massive 2380 mm² die, more than six times the size of the GB203's 378 mm². The MI355X packs 185,000 million transistors total, roughly four times the RTX 5080 Mobile's 45,600 million, but spreads them across a much larger area.

Memory architecture reinforces the split. HBM3e on an 8192-bit bus is a high-bandwidth, high-capacity solution suited to large compute workloads. GDDR7 on a 256-bit bus is a conventional graphics memory setup suited to rendering and mobile power constraints. The MI355X's 288 GB capacity dwarfs the RTX 5080 Mobile's 16 GB, and its 8.19 TB/s bandwidth is roughly nine times the NVIDIA card's 896.0 GB/s.

The Verdict

The data points to two products with essentially no overlap in intended function. The AMD Instinct MI355X is a compute accelerator with no graphics capabilities, no recorded benchmarks, and specifications that prioritize raw throughput: 78.64 TFLOPS FP32, 8.19 TB/s bandwidth, and 288 GB of memory. Its 1400 W TDP and OAM Module form factor place it in server or data center contexts. The absence of benchmark scores means its real-world performance cannot be quantified from the database, but its specification sheet indicates a device built for large-scale compute tasks.

The NVIDIA GeForce RTX 5080 Mobile is a mobile graphics processor with a full benchmark profile. Its average score of 38,349 and percentile rank of 81 demonstrate measurable performance against the rest of the database. Its nearest rivals sit within 0.9% in either direction, showing that it competes in a tight performance cluster. Its 80 W TDP and IGP form factor fit portable devices, and its API support, display outputs, RT cores, and tensor cores make it a general-purpose graphics solution.

Who should pick which comes down to the workload implied by the recorded data. The MI355X suits environments where FP32 compute, texture throughput, memory bandwidth, and memory capacity are the primary requirements, and where graphics output, ray tracing, and standard APIs are irrelevant. The RTX 5080 Mobile suits environments where rendering, API compatibility, mobile power limits, and verified benchmark performance matter. The RTX 5080 Mobile has the evidence of ten test scores behind it; the MI355X has only its specification fields. The choice between them is a choice between a compute accelerator and a graphics processor, and the data supports that distinction clearly.