Rubin vs MI355X: specifications compared
Comparison of Rubin and MI355X based on data from the manufacturer or provider.
According to the manufacturer, Rubin and MI355X differ mainly in memory bandwidth (Rubin: 22,000 GB/s, MI355X: 8,000 GB/s). The architecture also differs: Rubin versus CDNA 4. In the Clouwino points, which are calculated from the specifications, Rubin gets 92 and MI355X gets 68. Checked on 19 October 2026, no prices.
How are the points calculated?
Clouwino points are an arithmetic summary of the specifications the manufacturer states, on a scale of 0 to 100. It is not a benchmark and not a judgement on quality or suitability: a product with fewer points may suit your situation better. Products are compared with other products of the same type. For each property we count how far a product sits between the lowest and highest value in the group:
- FP32 compute (for: consumer), carries heavy weight
- Memory (for: consumer), carries heavy weight
- Memory bandwidth (for: consumer), carries heavy weight
- Compute units (for: consumer), carries light weight
- Boost clock (for: consumer), carries light weight
- Memory (for: professional and data centre), carries medium weight
- Memory bandwidth (for: professional and data centre), carries medium weight
- FP16/BF16 (for: professional and data centre), carries heavy weight
- FP8 (for: professional and data centre), carries medium weight
- FP64 (for: professional and data centre), carries medium weight
If too much data is missing, we do not show points. Points are relative: when a new product is added, they can shift. Read more at how we compare.
Rubin and MI355X side by side
| Specificatie | NVIDIA Rubin (per GPU) | AMD Instinct MI355X |
|---|---|---|
| Overview | ||
| Clouwino points | 92 punten | 68 punten |
| General | ||
| Architecture | Rubin | CDNA 4 |
| Manufacturing process | Not stated by the manufacturer | TSMC 3nm | 6nm FinFET |
| Form | Not stated by the manufacturer | OAM |
| Launch | Not stated by the manufacturer | 2025-06 |
| Compute | ||
| FP32 compute | 130 TFLOPS | 157,3 TFLOPS |
| FP64 | 33 TFLOPS | 78,6 TFLOPS |
| FP16/BF16 | 4.000 TFLOPS | 2.500 TFLOPS |
| FP8 | 17.500 TFLOPS | 5.000 TFLOPS |
| FP4 | 35.000 TFLOPS | 10.100 TFLOPS |
| Performance notes | FP16/BF16 4 PFLOPS (4000 TFLOPS) DENSE; FP8/FP6 training 17.5 PFLOPS (17500 TFLOPS) DENSE; FP4 = NVFP4 training 35 PFLOPS (35000 TFLOPS) DENSE. NVFP4 inference 50 PFLOPS (50000 TFLOPS) is SPARSE. TF32 2 PFLOPS dense, INT8 250 TOPS dense, FP32 SGEMM 400 TFLOPS and FP64 DGEMM 200 TFLOPS dense. FP32 130 and FP64 33 TFLOPS without a label. Values converted from PFLOPS to TFLOPS (unit only, no recalculation). | FP16/BF16 matrix: 2.5 PFLOPS dense (5 PFLOPS sparse). OCP-FP8 matrix: 5 PFLOPS dense (10.1 PFLOPS sparse). MXFP4: 10.1 PFLOPS, in AMD's dense column; no sparsity figure stated. MXFP6 10.1 PFLOPS. FP64 78.6 TFLOPS (vector and matrix), FP32 157.3 TFLOPS. PFLOPS converted to TFLOPS (unit only). Note: the page extraction did not explicitly label MXFP4/FP16 vector; check the dense/sparse columns manually if necessary. |
| Memory | ||
| Memory | 288 GB | 288 GB |
| Memory type | HBM4 | HBM3E |
| Memory bandwidth | 22 TB/s | 8 TB/s |
| Power and connections | ||
| Power (board power or TDP) | Not stated by the manufacturer | 1.400 W |
| GPU interconnect | NVLink 6: 3,6 TB/s | 7x Infinity Fabric, 153 GB/s per link; PCIe 5.0 x16; scale-out 128 GB/s (1 link) |
| Multiple instances | Not stated by the manufacturer | Not stated by the manufacturer |
Note: Figures per GPU from the HGX page. CONTRADICTORY: the Vera Rubin NVL72 page states 19.2 TB/s memory bandwidth and 3 TB/s NVLink; the HGX page and NVIDIA developer blog (21 July 2026) state 22 TB/s and 3.6 TB/s. The HGX/blog values are used here. TDP, process node, form factor and launch date not published (NVIDIA: 'ramping into full production'). No separate datasheet PDF was opened. A100 not included (space reserved for Rubin).
Note: Figures per GPU; TBP 1400 W (passive & active cooling). Launch date 12 June 2025. Sister product MI350X (also launched 12 June 2025): 288 GB HBM3E, 8 TB/s, TBP 1000 W, FP64 72.1 TFLOPS, FP16 matrix 2.3 PFLOPS dense (4.6 sparse), FP8 4.6 PFLOPS dense (9.2 sparse), MXFP4 9.2 PFLOPS. Partitioning not described (SR-IOV only). TF32 via software emulation.
Main differences between Rubin and MI355X
These are the differences the manufacturer lists in the specifications. The full table is further down.
- Memory bandwidth: Rubin 22,000 GB/s, MI355X 8,000 GB/s. Rubin lists about 2.8 times as much.
- Architecture: Rubin Rubin, MI355X CDNA 4.
- Memory type: Rubin HBM4, MI355X HBM3E.
What should you look at when choosing?
A higher number is not better for everyone. It depends on what you want to use it for.
- Memory bandwidth. Higher bandwidth means data can move to and from memory faster.
Also look at the rest of your system, such as power supply, cooling and software. Real-world performance depends on more than the specifications alone.
What do the Clouwino points say?
Rubin gets 92 points and MI355X gets 68 points. The points are calculated from the manufacturer’s specifications, within the same kind of products. They are not benchmark scores and say nothing about price or availability. Read how we calculate them at How we compare.
Frequently asked questions
What is the difference between Rubin and MI355X?
According to the manufacturer, Rubin and MI355X differ mainly in memory bandwidth (Rubin: 22,000 GB/s, MI355X: 8,000 GB/s). The architecture also differs: Rubin versus CDNA 4. In the Clouwino points, which are calculated from the specifications, Rubin gets 92 and MI355X gets 68.
Which one has the highest memory bandwidth?
According to the manufacturer, Rubin lists the highest memory bandwidth: 22,000 GB/s versus 8,000 GB/s.
What do Rubin and MI355X cost?
Clouwino does not show prices. You can see the current price and availability with the partner, via the button on the product page.
Where does the data come from?
The specifications come from the manufacturers' official pages and were checked on 19 October 2026. The sources are at the bottom of this page.
Last updated on
