Casper.Dik at Sun.COM wrote: > I'm not yet convinced that we need to get rid of the contents file > to get the performance we are after; the last prototype we did broke > badly for several reasons (excessive memory use, broken backward > compatibility).
Watch next time during an install; initial packages are added quickly and as time goes on the system runs slower and slower. Towards the end of install we're write 15MB to disk to add a 100k package. What I'd like to see happen here is that the first read of /var/sadm/install/contents causes a daemon to synchronously construct a cached, read-only version of the contents file from the actual contents information; the same file would be returned to others until pkgadd/pkgrm occurs mandating the creation of an new file. The Solaris packaging tools would not use this interface; it would be provided read-only for legacy apps and fingers. We don't support running previous versions of packaging tools on newer versions of Solaris; the Solaris 9 version of pkgadd would not deal well w/ zones, for example. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts
