ZFS, Actually Storage you can finally reason about.

Where the speed actually comes from

chain

5 steps, in order — start anywhere

  1. The ARC ZFS's reading cache—the reason your machine's memory looks full, and why that's the system working, not leaking.
  2. L2ARC A second-tier cache on a fast drive—not free speed, because indexing it spends the memory cache that's actually fast. A measured fix for a proven problem, not an upgrade.
  3. ZIL and SLOG Not a fast lane for writes—a diary of promises, written constantly and read exactly once: after a crash. A SLOG just moves the diary to a faster drive, and only promise-me-now writes ever use it.
  4. Recordsize The size of the chunks ZFS stores files in—adjustable per dataset. It matters when programs change small pieces inside huge files, and changing it only affects files written afterward.
  5. The Free-Space Discipline On ZFS, empty space isn't spare room—it's the workshop floor every change is made on. Fill the pool and it gets permanently grumpier.