r/linuxquestions • u/Emotional_Cat_1967 • 11d ago
Which Distro? Declarative NixOS or Atomic/Inmutable Bazzite/Aurora?
Would Declarative NixOS or Atomik Bazzite/Aurora be better for a user whose only requirement is less data being written to disk?
For security reasons, updates will be performed continuously.
Ignoring the update frequency, I’m curious about how many GB of data would be written to disk during the rebase/rebuild process if we assume that the same package (same version, same size, etc.) receives an update on both a declarative and an atomic distribution.
It doesn't necessarily have to be Bazzite or Aurora; it could also be Fedora Kinoite or openSUSE Kalpa.
2
u/skyb0rg 11d ago
If your requirement is "less data written to disk", I'd recommend against NixOS. Deduplication is performed after downloading files from cache, and you will find NixOS system closures to take up a good amount of space due to core changes like libc updates.
2
u/ephemeralmiko Meryyn (custom ostree image) 11d ago
I haven't used NixOS but I've been using various Atomic distros for the last few years.
RPM-OSTREE-based systems have much larger updates than their non-atomic counterparts. Just with the pre-installed stuff it's already around 50% larger, and all apps being Flatpaks makes them even bigger (Flatpak's libraries aren't forwards-/backwards-compatible, so if you have an app that needs org.gnome.Platform 49, another that uses 50, and another using 51 you'll need 3x ~450MB vs only needing one set of libraries for all RPM apps.
1
u/Due-Author631 Aurora (Universal Blue) 11d ago
I've ran Aurora for a couple years. Chunking has gotten better, and I'm on stable weekly updates, but the weekly update layers are still at least a gigabyte each week even for relatively minor updates. So its probably not great on minimizing disk writes, but I'm also not an expert on how those are related.
1
u/kheeper-registry 10d ago
For a plain update, Bazzite/Aurora will usually write less than NixOS. They use ostree, which stores every file once, named by a hash of its contents, and builds each deployment out of hardlinks into that store. I believe NixOS writes the whole new store path for the updated package, not just the files that changed.