Adrian, I agree. This is a good opportunity to discuss performance measurement issues.
However, you asked if I would fix your particular issues while fixing the bug that Mike found. I don't want to mislead anybody, so my response was simply that I don't presently have the time to address these additional issues. Please understand that although I'm not able work on this, this doesn't mean that your concerns are without merit. -j On Wed, Oct 18, 2006 at 07:13:08PM -0700, adrian cockcroft wrote: > I understand, but since this is "perf-discuss" I thought it was a good > opportunity to discuss this performance measurement issue. > > Thanks Adrian > > On 10/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >Adrian, > > > >I agree that these metrics would be useful and nice to have; however, > >their implementation is outside of the scope of what I intend to > >address with this fix. > > > >I'm simply fixing the functional regression in the kstats. I can't, in > >good faith, make improvements to microstate accounting and prstat as > >part of this bug. That work needs to be a separate RFE. I don't > >currently have the time to address the issues that would be part of the > >separate RFE. Although, if someone else is interested in doing this > >work, I'd be happy to provide guidance. > > > >-j > > > >> Sure, I saw what you proposed, but the real problem that we have is > >> that machines get io-bound and we should have metrics in Solaris that > >> tell us 1) a machine is io-bound, 2) which disks are responsible, and > >> 3) which processes are being blocked > >> > >> vmstat b is an approximation to the number of threads that are > >> blocked, a microstate and dispay via prstat would let us see which > >> threads are being blocked. There are even some unused slots in the > >> microstate data structure, so it can be fixed without breaking > >> backwards compatability. _______________________________________________ perf-discuss mailing list perf-discuss@opensolaris.org
