Supercomputers/Systems/Neo
USA · operational · mixed
Neo
Also known as LLNL Neo
Operated by Lawrence Livermore National Laboratory at Livermore Computing Center .
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: 1092 of 1153 systems have a readable citation that names them, and 40 are genuinely weakly sourced. Every claim carries its source and a confidence tier. Treat anything below verified as a lead, not a citation.
Measured performance
- Rmax
- -
- Rpeak
- -
- Rmax ÷ Rpeak
- -
- Cores
- 448
- Power
- -
- Per watt
- - GF/W
Figures are as last publicly reported for the configuration described below, not a live measurement. Where a system was upgraded in place, the post-upgrade configuration is shown and the earlier one appears in the timeline.
What this machine is made of
One row per supplier relationship. “Supplier at build” is the company that shipped the part at the time; where that company has since been acquired, the parent it rolls up to today is shown beside it. That distinction is what makes ticker-level aggregation possible across a thirty-year dataset.
| Role | Part | Supplier at build | Quantity | Confidence | Source |
|---|---|---|---|---|---|
| Accelerator | NVIDIA H200 SXM Accelerators CUDA (Hopper GH100) · 16,896C · 1.98 GHz · TSMC 4N · 700 W NVIDIA H200, 8 per node, 32 GPUs in total | NVIDIA | 32 reported | Reported | hpc.llnl.gov |
| CPU | - Intel 8480+, 112 cores per node, 4 batch nodes | Intel | 4 reported | Reported | hpc.llnl.gov |
| Interconnect | NVIDIA InfiniBand NDR (Quantum-2) Interconnect Fat tree or dragonfly+ · 400 Gb/s per port · Under 0.6 microseconds Nvidia Mellanox NDR 400 | NVIDIA | - | Reported | hpc.llnl.gov |
| Operating system | Tri-Lab Operating System Stack Operating systems Linux distribution, RHEL-derived, HPC-tuned · Open source, LLNL-maintained TOSS 4 | Lawrence Livermore National Laboratory | - | Reported | hpc.llnl.gov |
The read
A four-node NVIDIA H200 system in Livermore's Secure Computing Facility, commissioned in 2026 under the ASC programme and classed 'Mixed' on LLNL's platform list, with Penguin, Dell and NVIDIA named as vendors. LLNL's page gives 4 batch nodes of Intel 8480+ (112 cores per node, 448 in all, 1,000 GiB per node) with 8 H200 GPUs each (32 in total) on NVIDIA Mellanox NDR 400, running TOSS 4 under Slurm, and quotes 28.4 PFlop/s CPU and 272 PFlop/s GPU peak, 300.4 combined. The GPU figure is a low-precision AI peak, not double precision, so no FLOPS field is recorded. No TOP500 entry was found.
Timeline
- 2026 First operational source
Site & facility
Livermore Computing Center
- Location
- Livermore, CA, USA
- Cooling
- Direct liquid cooling (warm water)
- Commissioned
- 1996
Change history
- 2026-10-04 Added Neo (llnl)
Source check
We fetched this system's own citations and recorded whether each page actually mentions it. This is a corroboration signal, not a fact check, and it is published so you can see how well the sourcing holds up rather than take it on trust.
Every source cited on this page was readable, and none of them mentions this system. They are cited at page granularity, normally because no stable deep link could be found. That is a real weakness in this row and it is why the system carries a confidence tier below verified. See how this check works.
| Cited source | Result | Found on the page |
|---|---|---|
| hpc.llnl.gov | does not name this system | NVIDIA H200 SXM, Tri-Lab Operating System Stack · counts: 32 |
| hpc.llnl.gov | does not name this system | NVIDIA H200 SXM, Tri-Lab Operating System Stack · counts: 32 |
Checked 2026-10-09 by pnpm verify. Re-run it and the table changes with the web.
Further reading
Inside a node
Why accelerators exist, what the memory hierarchy costs, and how the CPU and accelerator merged onto one package.
The interconnect
Topologies, why latency and tail behaviour matter more than bandwidth, and how the fabric market consolidated.
Programming a supercomputer
The software stack beneath the application, and why the OS is now a sovereignty signal as much as a technical choice.