You can avoid the not-fast problem by rsyncing /usr/bin and /usr/lib (and parts of
/usr/share?) into battery-backed/flash RAM, so most of the time very few writes would be
needed.
(Obviously rsync for this purpose is a kludge; some sort of replicated write at the kernel
level seems preferable. Perhaps dm mirroring could do this, but it'd be forced to replicate
all of /usr into flash, whether we care about it or not...)
Posted Apr 1, 2008 18:36 UTC (Tue) by dmarti (subscriber, #11625)
[Link]
Or do something like the "Ramback" patch from Daniel Phillips (LWN article): "The core idea behind Ramback is that all of that memory is turned into a ramdisk, but with a persistent device attached to it. In normal conditions, all application I/O involves only the ramdisk, and is, thus, quite fast."