I'm generally happy with the zone level kstat data available today. I think that maintaining the kind of granular data your talking about via kstats is excessive... but I'd be interested in other opinions.
Using the existing kstats in conjunction with a process that "rolls up" daily extended accounting data would allow me to see not just how much CPU and memory a zone is using, but what processes they are most actively running... a historical top 10 workloads by day, etc. That could be handy. One thing that does bug me is that quantifying how much performance impact exacct has is very hard to determine. I'd like more research there. (The same goes for BSM actually.) As for improving the visability into sys%, I totally agree. As the Solaris kernel gets more and more complex I think we're all seeing a lot more system time on our production systems and quantifying what that is, even with DTrace, is very complex. benr. -- This message posted from opensolaris.org
