> Cloning somewhat helps with the disk footprint, but > the savings there will > get lower over time as more and more binaries are > upgraded. We clearly > have to work on that. The memory saving of sparse > root zones was nothing > to sniff at.
So a share-able executable, library, or object had its read-only parts only resident once across the global and multiple sparse zones (sharing a copy of the same object), but now (even if the zone resides in a ZFS clone) is loaded once for each (non-sparse) zone? I bet that will be a big problem on for example a workstation using Trusted Solaris extensions, where each label corresponds to a zone; since the set of libraries for GUI applications tends to be rather large (esp. with GTK+/GNOME as compared to the old days of Motif). Probably affects CPU cache, too. Yuck. -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
