Supercomputers/Systems/Petrichor
Australia · operational · hpc
Petrichor
Also known as CSIRO Petrichor HPC
Operated by CSIRO .
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
- -
- 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 |
|---|---|---|---|---|---|
| CPU | - AMD Milan, 400+ nodes and 25,000+ cores | AMD | - | Reported | arxiv.orgcsiro.au |
The read
CSIRO's CPU cluster that replaced the Ruby and Pearcey systems, described by CSIRO as having over 400 server nodes, more than 25,000 cores and 235 TB of memory, three times the capacity of Ruby and Pearcey combined, and housed in the same pod as the Bracewell cluster. CSIRO's page (last updated April 2022) does not name the CPU, vendor, interconnect or site. A 2025 arXiv survey of Australian institutions lists it as AMD Milan, 400+ nodes and 25,000+ cores. It is distinct from CSIRO's GPU system Virga. No FLOPS figure is published.
Timeline
No dated events recorded.
Change history
- 2026-10-02 Added Petrichor, CSIRO's CPU cluster
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.
Checked 2026-10-09 by pnpm verify. Re-run it and the table changes with the web.