------- Forwarded Message From: Jim Mauro <[EMAIL PROTECTED]> Date: Thu, 13 Sep 2007 14:38:15 -0700
> My priority item for CPU observability right now is accurate utilization > accounting. The bundled Solaris tools that we rely on report virtual CPU > utilization, and customers (and performance engineers! :^) need utilization > of actual execution resources (cores). > Any processor technology that implements the notion of a thread or strand > that is described as a CPU by Solaris is an issue. That's Niagara, > Niagara-2, > and all the OPL boxes. Similar problems are looming in the AMD and Intel > space. > > I had an email dialogue going with various people about this > (as a result from a current customer issue), and really believe we need a > proper fix for this. From my standpoint, I see 2 phases to this; > - A short term fix to get something out to customers soon. I'm overdue > to discuss this with Ravi, and am thinking we can re-implement his > corestat tool in C and make it work across various platforms. > - A long term fix, potentially built on CPUfs, that will propogate up to > fix mpstat, sar, vmstat, etc... > > That, IMHO, is a clear top priority for our first round of improving CPU > observability. > As an aside, did you guys ping Denis? I seem to recall that Denis (and > Richard) implemented a CPUfs when they did cachestat. ------- End of Forwarded Message _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
