Supercomputers/Systems/BA-HPC C2
Egypt · operational · hpc
BA-HPC C2
Also known as Bibliotheca Alexandrina HPC Cluster 2
Operated by Bibliotheca Alexandrina at Bibliotheca Alexandrina HPC Facility .
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
- 118.47 TFlop/s
- Rmax ÷ Rpeak
- -
- Cores
- 1,968
- Power
- 53.32 kW
- 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 |
|---|---|---|---|---|---|
| Integrator | - Huawei X6800 high-density servers | Huawei | - | Reported | huawei.com |
| Accelerator | - NVIDIA Tesla K80, 1 per GPU node, 16 GPU nodes | NVIDIA | 16 reported | Reported | hpc.bibalex.org |
| CPU | - 2x Intel Xeon E5-2680 v3 per CPU node, 82 CPU nodes | Intel | 82 reported | Reported | hpc.bibalex.org |
| Interconnect | Mellanox InfiniBand QDR Interconnect Fat tree · 40 Gb/s per 4x port 40-Gbps QDR InfiniBand | Mellanox NVDANASDAQ
rolls up to NVIDIA | - | Reported | hpc.bibalex.orghuawei.com |
The read
Egypt's Bibliotheca Alexandrina operates its own HPC facility inside the library's International School of Information Science. BA-HPC C2, installed in August 2016, is a Huawei-built cluster of 82 CPU-only nodes (dual Xeon E5-2680 v3, 1,968 cores total) plus 16 GPU nodes (dual Xeon E5-2630 v3 hosts, one NVIDIA Tesla K80 each) on 40 Gbps QDR InfiniBand with a Lustre-based 288 TB shared filesystem, for a theoretical peak of 118.47 TFlop/s (88.55 TFlop/s CPU plus 29.92 TFlop/s GPU). The library's own HPC documentation and Huawei's original press release independently agree on the roughly 118 TFlop/s peak figure, the 288 TB storage capacity and the InfiniBand fabric, so the tier is verified for those facts; the detailed node breakdown and per-node processor models come from the library's page alone. It has never appeared on TOP500. No HPL run is published, so rmax is left blank and the peak figure is recorded as vendor_peak.
Site & facility
Bibliotheca Alexandrina HPC Facility
- Location
- Alexandria, Egypt
- Commissioned
- 2016
Change history
- 2026-09-24 BA-HPC C2 added (Egypt)
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.
One cited source was readable and does not mention this system; another could not be read because the host returned a bot challenge. The unreadable one may well be fine, so this is weaker evidence than a corroborated row and much stronger than an unsupported one. See how this check works.
| Cited source | Result | Found on the page |
|---|---|---|
| hpc.bibalex.org | could not be fetched | - |
| huawei.com | does not name this system | Mellanox InfiniBand QDR |
Checked 2026-10-09 by pnpm verify. Re-run it and the table changes with the web.
Further reading
Inside a node
Latency-optimised versus throughput-optimised processors, NUMA, and the end of the host-to-device copy.
The interconnect
Topologies, why latency and tail behaviour matter more than bandwidth, and how the fabric market consolidated.
Operating a supercomputer
Acceptance testing, why "installed" and "in production" are six months apart, and the machine lifecycle.