AI chips compared: H100, B200, Rubin, MI355X, TPU and Trainium accelerator specs
Specs of data-center AI accelerators from every vendor, copied from each vendor’s own datasheet.
| Name | Vendor | Memory | Memory bandwidth (TB/s) | FP8 (TFLOPS) | Status |
|---|---|---|---|---|---|
| AMD Instinct MI300X | AMD | 192 GB HBM3 | 5.3 TB/s | 2,610 TFLOPS | Shipping |
| AMD Instinct MI325X | AMD | 256 GB HBM3E | 6 TB/s | 2,610 TFLOPS | Shipping |
| AMD Instinct MI355X | AMD | 288 GB HBM3E | 8 TB/s | 5,000 TFLOPS | Shipping |
| AMD Instinct MI430X | AMD | 432 GB HBM4 | 23.3 TB/s | Announced | |
| AMD Instinct MI455X | AMD | 432 GB HBM4 | 23.3 TB/s | 20,100 TFLOPS | Announced |
| AWS Trainium2 | AWS | 96 GiB HBM | 2.9 TB/s | 1,299 TFLOPS | Shipping |
| AWS Trainium3 | AWS | 144 GB HBM3e | 4.9 TB/s | 2,517 TFLOPS | Shipping |
| Cerebras WSE-3T (CS-4) | Cerebras | 44 GB on-wafer SRAM | 43,200 TB/s | Announced | |
| Google TPU 8i | 288 GB HBM | 8.601 TB/s | Announced | ||
| Google TPU 8t | 216 GB HBM | 6.528 TB/s | Announced | ||
| Google TPU7x (Ironwood) | 192 GB HBM | 7.37 TB/s | 4,614 TFLOPS | Shipping | |
| Huawei Ascend 950DT | Huawei | 144 GB HiZQ 2.0 (Huawei HBM) | 4 TB/s | 1,000 TFLOPS | Announced |
| Huawei Ascend 960 (Atlas 960E SuperPoD) | Huawei | Up to 1 PB HBM per Atlas 960E SuperPoD (4,096 NPUs) | 2,000 TFLOPS | Announced | |
| Intel Gaudi 3 | Intel | 128 GB HBM2e | 3.7 TB/s | 1,678 TFLOPS | Shipping |
| Meta MTIA 200 | Meta | 128 GB LPDDR5 (off-chip) + 256 MB SRAM | 0.205 TB/s | Shipping | |
| Microsoft Maia 200 | Microsoft | 216 GB HBM3e | 7 TB/s | 5,000 TFLOPS | Shipping |
| Nvidia B200 (Blackwell) | Nvidia | Up to 192 GB HBM3E (180 GB per GPU in HGX B200) | 8 TB/s | 5,000 TFLOPS | Shipping |
| Nvidia B300 (Blackwell Ultra) | Nvidia | 288 GB HBM3E | 8 TB/s | 5,000 TFLOPS | Shipping |
| Nvidia GB200 NVL72 | Nvidia | 13.4 TB HBM3E (72 GPUs) | 576 TB/s | 720,000 TFLOPS | Shipping |
| Nvidia GB300 NVL72 | Nvidia | 20 TB HBM3E (72 GPUs) | 576 TB/s | 720,000 TFLOPS | Shipping |
| Nvidia Groq 3 LPX | Nvidia | 128 GB SRAM per rack (256 LPUs) | 40,000 TB/s | In production | |
| Nvidia H100 SXM | Nvidia | 80 GB HBM3 | 3.35 TB/s | 3,958 TFLOPS | Shipping |
| Nvidia H200 SXM | Nvidia | 141 GB HBM3e | 4.8 TB/s | 3,958 TFLOPS | Shipping |
| Nvidia Rubin GPU | Nvidia | 288 GB HBM4 | 22 TB/s | 17,500 TFLOPS | In production |
| Nvidia Vera Rubin NVL72 | Nvidia | 20.7 TB HBM4 (72 GPUs) | 1,580 TB/s | 1,260,000 TFLOPS | In production |
This table lists AI accelerator specs for data-center chips from Nvidia, AMD, Google, AWS, Intel, Cerebras, Huawei, Microsoft and Meta: Hopper H100 and H200, Blackwell B200 and B300, GB200 and GB300 NVL72 racks, the Rubin GPU and Vera Rubin NVL72, Instinct MI300X through MI455X, TPU Ironwood and TPU 8, Trainium2 and Trainium3, Gaudi 3, Cerebras WSE-3T, Ascend, Maia 200 and MTIA.
Every number comes from the vendor’s own datasheet, product page, technical documentation or announcement, linked on each entry with the date it was checked. We copy figures as the vendor states them. Vendors quote FP8 and FP4 throughput either with sparsity or without it (dense); each entry’s precision note says which, because the two can differ by a factor of two. Where a vendor publishes no figure for a field, the field is left blank rather than estimated.
Some vendors publish specs per chip, others per board, rack or pod. The form factor column says which level a row describes, so rack-scale rows (NVL72, CS-4, Groq 3 LPX) are not directly comparable with single chips. Memory is in GB, bandwidth in TB/s, FP8 in TFLOPS and FP4 in PFLOPS.
The table is checked against vendor sources three times a week. For launch coverage see AI chip news, for cloud rental rates per GPU-hour see GPU prices, and for where these chips are being deployed see AI data centers. How we source data is described in our editorial standards.
Source
Every figure is taken from the vendor’s own datasheet, product page, technical documentation or announcement, linked on each chip with the date it was last checked. How we pick and check sources: editorial standards.