Supercomputers/Analysis/Silicon generation decay
Analysis 07
Refresh cadence and silicon generation decay
Of the accelerator generations in this dataset that have actually left the installed base, the median stayed 3 years. The longest-lived is Tesla Dojo D1 at 3 years, a part released in 2021 and still running well into the following decade. The median gap between a part being released and appearing in a large system is 1 year, which is the number most often assumed to be zero.
Phase 1 seed dataset, compiled by hand. These rows were built from public operator, laboratory and vendor sources. A mechanical second-reader pass has since fetched every cited source: 1263 of 1345 systems have a readable citation that names them, and 56 are genuinely weakly sourced. Every claim carries its source and a confidence tier. Treat anything below verified as a lead, not a citation.
Read the shape, not the spikes. This is the installed base of the 1345 systems in this dataset: a curated seed chosen for supply-chain diversity, not a census of the market. At that sample size one machine entering or leaving service moves a share line by tens of points, so year-to-year jumps are composition effects rather than market events. The multi-year trends are the part worth quoting; the individual steps usually have one system's name on them, and the table view under the chart will tell you which.
- NVIDIA
- AMD
- Intel
- Other suppliers
Table view: Accelerator generations in the installed base
| Generation | Supplier | Released | In service | Years | Release→deploy | Peak installed | Peak year | Systems |
|---|---|---|---|---|---|---|---|---|
| IBM PowerXCell 8i | IBM | 2008 | 2008–2026+ | 19 | 0 | 2.02 PFlop/s | 2009 | 4 |
| ATI Radeon HD 4870 X2 | AMD | 2009 | 2009–2026+ | 18 | 0 | 563.10 TFlop/s | 2009 | 1 |
| NVIDIA Tesla M2050 | NVIDIA | 2010 | 2010–2026+ | 17 | 0 | 3.76 PFlop/s | 2010 | 3 |
| NVIDIA Tesla K20X | NVIDIA | 2012 | 2011–2026+ | 16 | -1 | 24.43 PFlop/s | 2015 | 10 |
| Intel Xeon Phi 31S1P | Intel | 2013 | 2013–2023+ | 11 | 0 | 63.51 PFlop/s | 2014 | 2 |
| Intel Xeon Phi 7250 (Knights Landing) | Intel | 2016 | 2013–2026+ | 14 | -3 | 58.29 PFlop/s | 2017 | 6 |
| Intel Xeon Phi SE10P | Intel | 2012 | 2013–2026+ | 14 | 1 | 5.17 PFlop/s | 2013 | 1 |
| AMD FirePro S9150 | AMD | 2014 | 2014–2026+ | 13 | 0 | 316.70 TFlop/s | 2014 | 1 |
| Anton 2 ASIC | D. E. Shaw Research | 2014 | 2014–2026+ | 13 | 0 | 0.0 GFlop/s | 2014 | 1 |
| NVIDIA A100 SXM4 40GB | NVIDIA | 2020 | 2014–2026+ | 13 | -6 | 453.9 PFlop/s | 2023 | 43 |
| NVIDIA H100 SXM5 | NVIDIA | 2022 | 2014–2026+ | 13 | -8 | 2.03 EFlop/s | 2025 | 79 |
| NVIDIA Tesla P100 | NVIDIA | 2016 | 2014–2026+ | 13 | -2 | 68.70 PFlop/s | 2018 | 27 |
| NVIDIA Tesla V100 | NVIDIA | 2017 | 2014–2026+ | 13 | -3 | 484.1 PFlop/s | 2021 | 83 |
| PEZY-SC2 | PEZY Computing | 2017 | 2016–2020+ | 5 | -1 | 20.76 PFlop/s | 2017 | 5 |
| NUDT Matrix-2000 | NUDT | 2017 | 2018–2018+ | 1 | 1 | 61.44 PFlop/s | 2018 | 1 |
| NVIDIA A100 SXM4 80GB | NVIDIA | 2020 | 2018–2026+ | 9 | -2 | 54.16 PFlop/s | 2022 | 11 |
| NVIDIA H100 80GB PCIe | NVIDIA | 2022 | 2018–2026+ | 9 | -4 | 4.83 PFlop/s | 2024 | 4 |
| Google TPU v4 | Alphabet | 2020 | 2020–2026+ | 7 | 0 | 0.0 GFlop/s | 2020 | 2 |
| NEC SX-Aurora TSUBASA Vector Engine | NEC | 2018 | 2020–2026+ | 7 | 2 | 51.28 PFlop/s | 2025 | 5 |
| NVIDIA A100 (in DGX A100) | NVIDIA | - | 2020–2026+ | 7 | - | 83.70 PFlop/s | 2023 | 13 |
| NVIDIA H200 SXM | NVIDIA | 2024 | 2020–2026+ | 7 | -4 | 1.07 EFlop/s | 2026 | 45 |
| NVIDIA L40S | NVIDIA | 2023 | 2020–2026+ | 7 | -3 | 0.0 GFlop/s | 2020 | 19 |
| Preferred Networks MN-Core (1st generation) | Preferred Networks | 2018 | 2020–2026+ | 7 | 2 | 2.18 PFlop/s | 2020 | 1 |
| AMD Instinct MI250X | AMD | 2021 | 2021–2026+ | 6 | 0 | 2.38 EFlop/s | 2024 | 15 |
| Cerebras WSE-3 | Cerebras | 2024 | 2021–2026+ | 6 | -3 | 0.0 GFlop/s | 2021 | 4 |
| Huawei Ascend 910 | Huawei | 2019 | 2021–2023+ | 3 | 2 | 0.0 GFlop/s | 2021 | 3 |
| NVIDIA B200 SXM | NVIDIA | 2024 | 2021–2026+ | 6 | -3 | 472.6 PFlop/s | 2026 | 31 |
| Cerebras CS-2 (WSE-2) | Cerebras | - | 2022–2026+ | 5 | - | 0.0 GFlop/s | 2022 | 5 |
| NVIDIA A100 SXM4 64GB | NVIDIA | 2020 | 2022–2026+ | 5 | 2 | 244.7 PFlop/s | 2022 | 2 |
| Graphcore IPU | Graphcore | 2020 | 2023–2025+ | 3 | 3 | 7.94 PFlop/s | 2023 | 1 |
| Intel Data Center GPU Max 1550 | Intel | 2023 | 2023–2026+ | 4 | 0 | 1.03 EFlop/s | 2024 | 5 |
| NVIDIA GH200 Grace Hopper Superchip | NVIDIA | 2023 | 2023–2026+ | 4 | 0 | 2.26 EFlop/s | 2026 | 27 |
| Tesla Dojo D1 | Tesla | 2021 | 2023–2025 | 3 | 2 | 0.0 GFlop/s | 2023 | 1 |
| AMD Instinct MI210 | AMD | 2022 | 2024–2026+ | 3 | 2 | 54.12 PFlop/s | 2025 | 5 |
| AMD Instinct MI300A | AMD | 2023 | 2024–2026+ | 3 | 1 | 2.76 EFlop/s | 2026 | 15 |
| AMD Instinct MI300X | AMD | 2023 | 2024–2026+ | 3 | 1 | 114.5 PFlop/s | 2025 | 2 |
| Google TPU v5p | Alphabet | 2023 | 2024–2026+ | 3 | 1 | 0.0 GFlop/s | 2024 | 5 |
| Google TPU v6e (Trillium) | Alphabet | 2024 | 2024–2026+ | 3 | 0 | 0.0 GFlop/s | 2024 | 3 |
| Google TPU7x (Ironwood) | Alphabet | 2025 | 2024–2026+ | 3 | -1 | 0.0 GFlop/s | 2024 | 4 |
| NVIDIA H100 SXM5 94GB | NVIDIA | 2023 | 2024–2026+ | 3 | 1 | 220.6 PFlop/s | 2024 | 11 |
| AMD Instinct MI325X | AMD | 2024 | 2025–2026+ | 2 | 1 | 0.0 GFlop/s | 2025 | 1 |
| AWS Trainium2 | Amazon | 2024 | 2025–2026+ | 2 | 1 | 0.0 GFlop/s | 2025 | 3 |
| Groq LPU | Groq | 2023 | 2025–2025+ | 1 | 2 | 0.0 GFlop/s | 2025 | 3 |
| Huawei CloudMatrix 384 | Huawei | 2025 | 2025–2025+ | 1 | 0 | 0.0 GFlop/s | 2025 | 2 |
| NVIDIA GB200 NVL72 | NVIDIA | 2024 | 2025–2026+ | 2 | 1 | 22.21 PFlop/s | 2026 | 10 |
| NVIDIA GB300 NVL72 | NVIDIA | 2025 | 2025–2026+ | 2 | 0 | 0.0 GFlop/s | 2025 | 10 |
| AMD Instinct MI355X | AMD | 2026 | 2026–2026+ | 1 | 0 | 34.77 PFlop/s | 2026 | 2 |
| Huawei Ascend 910C | Huawei | - | 2026–2026+ | 1 | - | 0.0 GFlop/s | 2026 | 1 |
How this was calculated
A generation is present in a year if any system carrying it was in service that year. A system is in service from its first-operational date until it is retired.
Two modelling problems had to be fixed before this chart could be honest, and both are worth stating.
First, component edges originally had no time bounds, so a system that was rebuilt with
different silicon made both generations look present for its whole life. Tianhe-2 is the
case: Intel Xeon Phi from 2013, NUDT Matrix-2000 from 2018. Edges now carry optional
era_start and era_end dates, and without them this page would have
credited a discontinued Intel part with an extra seven years of installed life.
Second, a system recorded as operational with no retirement date means we found no
source saying it was retired, which is an absence of evidence, not evidence of absence.
Systems now carry a status_as_of date recording when the status was last supported
by a source. Tianhe-1A forces this: read naively it would credit a 2010 Fermi part with sixteen
years in service on the strength of a missing citation.
Spans that are still open are excluded from the median, because including a generation that has not finished would bias the figure downward: every currently-deployed part looks short-lived until it is retired. Only the 1 generations with a closed span contribute to the 3-year median.
“Peak installed” is the highest total Rmax of all systems carrying the part in any one year. It is a capability measure, not a unit count.
The read
The headline is how long generations last, and it is longer than the release cadence suggests. Vendors ship a new accelerator every eighteen months to two years; the installed base turns over on something closer to a seven-to-ten-year cycle. Kepler's K20X entered service in 2012 and was still running in 2021. The gap between those two clocks is where most of the confusion about “refresh cycles” lives: a procurement cycle and a product cycle are not the same cycle.
The second pattern is the release-to-deployment lag. Parts do not appear in leadership systems the year they launch; the median here is a year, and the exceptions run longer. That lag compounds with the announcement-to-first-light lag on the schedule page: a system announced around silicon that has not shipped is committing to two uncertainties at once.
The third is displacement, and the clearest case is not a technical one. Intel's Xeon Phi 31S1P has a closed span ending in 2018, and it did not end because something faster arrived: it ended because an export control blocked the upgrade path and NUDT substituted its own part. On this chart that is a generation dying at a policy boundary rather than a performance one, which is exactly the kind of thing a supply-chain view can show and a ranking cannot.
The bars at the right-hand edge are all open, which is the correct rendering and also the limitation. Every current generation looks short-lived because it has not finished yet. Nothing on the right third of this chart should be read as a lifespan.