Re: LWLock statistics collector

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Robert Lor <Robert(dot)Lor(at)Sun(dot)COM>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: LWLock statistics collector
Date: 2006-08-07 01:26:56
Message-ID: 20060807100812.525D.ITAGAKI.TAKAHIRO@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


Robert Lor <Robert(dot)Lor(at)Sun(dot)COM> wrote:

> CVS head now has the following LWLock probes, and more can easily be
> added. These probes can be enabled using the sample DTrace scripts at
> http://pgfoundry.org/projects/dtrace/
>
> lwlock-acquire
> lwlock-release
> lwlock-startwait
> lwlock-endwait
> lwlock-condacquire
> lwlock-condacquire-fail
>
> If anyone wants to have access to a Solaris machine to play with DTrace,
> let me know.

I assure you that DTrace is a powerful tool, but as for LWLock statistics,
can we gather them well with it? There is a "color coding" problem in the
persent dump-to-stderr and DTrace methods. I assume we want to gather the
statistics per resource (represented by LWLockKind in my patch), not per
LWLockId.

Even if we use DTrace, do we need some supports for coloring of lwlocks?

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2006-08-07 02:45:15 Re: 8.2 features status
Previous Message Andrew Dunstan 2006-08-06 23:33:25 installcheck-parallel

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-08-07 03:45:50 Re: [HACKERS] [PATCHES] log_statement output for protocol
Previous Message Tom Lane 2006-08-06 03:57:18 Re: Forcing current WAL file to be archived