Parts/Storage/Fujitsu FEFS
Why this part
Fujitsu's own Lustre-based appliance, and the fact that Fugaku names it explicitly is useful in itself: most of this dataset's storage rows are inferred from a system's era rather than stated by the operator. RIKEN's own architecture page describes a three-layer hierarchy: LLIO, a node-local NVMe accelerator, absorbs each job's burst traffic; FEFS is the large shared area everyone's data actually lives in; commercial cloud storage sits behind both as a third tier. FEFS is also the continuity between Fugaku and its predecessor, K computer, which used the same Fujitsu product a decade earlier, so the file system a user sees changed far less across that transition than the processor did.
Systems using this part
- Systems
- 3
- Rmax underneath
- 453.5 PFlop/s
- Units recorded
- -
| System | Role | Country | Units | System Rmax | Supplied by | Rank |
|---|---|---|---|---|---|---|
| Fugaku 2020-06 | Storage | Japan | - | 442.0 PFlop/s | Fujitsu | #54 → |
| HOKUSAI GreatWave 2015-04 | Storage | Japan | - | 990.00 TFlop/s | Fujitsu | #70 → |
| K computer 2011-06 | Storage | Japan | - | 10.51 PFlop/s | Fujitsu | #1 → |
“Units recorded” sums only the edges where a public source states a quantity. It is a floor, not a total, and should never be read as installed base.