Supercomputers/Systems/Baku (HLRS)
Germany · operational · hpc
Baku (HLRS)
Also known as Baku; HLRS NEC Nehalem Cluster
Operated by HLRS at HLRS, University of Stuttgart .
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
- 50.79 TFlop/s
- Rpeak
- 60.21 TFlop/s
- Rmax ÷ Rpeak
- 84.4%
- Cores
- 5,376
- Power
- 186 kW
- Per watt
- 0.3 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 |
|---|---|---|---|---|---|
| Integrator | - NEC HPC 140Rb-1 cluster, 700 nodes | NEC | - | Reported | top500.org |
| Accelerator | - NVIDIA Tesla S1070 GPU systems on 32 nodes | NVIDIA | - | Reported | top500.org |
| CPU | - Intel Xeon X5560 quad-core 2.8 GHz Nehalem, dual-socket nodes | Intel | - | Reported | top500.org |
| Operating system | Windows HPC Server 2008 Operating systems Windows Server kernel with HPC Pack job scheduler · Commercial license Windows HPC Server 2008 | Microsoft | - | Reported | top500.org |
The read
NEC Nehalem cluster at the High Performance Computing Center Stuttgart, listed by TOP500 as Baku (HWW/Universitaet Stuttgart). HLRS's 2009 platform page describes it as forming a heterogeneous platform with the NEC SX-9, with 62 TFlop/s peak, 700 nodes of dual-socket quad-core Xeon X5560 Nehalem at 2.8 GHz with 12 GB per node, 60 TB of shared Lustre scratch, InfiniBand and Gigabit Ethernet, and 32 nodes carrying NVIDIA Tesla S1070 GPUs. TOP500 lists a NEC HPC 140Rb-1 cluster with 5,376 cores running Windows HPC Server 2008 at 50.79 TFlop/s Rmax, 60.21 TFlop/s Rpeak and 186 kW, 77th in June 2009, then 94th, 110th, 159th and 305th in June 2011, its last appearance. The core counts differ between the two pages (5,376 against 700 nodes of 8 cores), so the tier is reported.
Timeline
Public list appearances
Pointers only: rank and edition, linking to the canonical entry. We do not reproduce list tables. See sourcing policy.
Site & facility
HLRS, University of Stuttgart
- Location
- Stuttgart, Germany
- Cooling
- Direct liquid cooling
- Commissioned
- 1996
Change history
- 2026-10-09 Added Baku (HLRS)
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 |
|---|---|---|
| web.archive.org | does not name this system | - |
| top500.org | does not name this system | Windows HPC Server 2008 |
Checked 2026-10-09 by pnpm verify. Re-run it and the table changes with the web.
Further reading
Operating a supercomputer
Acceptance testing, why "installed" and "in production" are six months apart, and the machine lifecycle.
Inside a node
Latency-optimised versus throughput-optimised processors, NUMA, and the end of the host-to-device copy.
Programming a supercomputer
The software stack beneath the application, and why the OS is now a sovereignty signal as much as a technical choice.