Re: LWLOCK_STATS - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: LWLOCK_STATS
Date
Msg-id 4F07FB0D.8000302@enterprisedb.com
Whole thread Raw
In response to LWLOCK_STATS  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: LWLOCK_STATS  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: LWLOCK_STATS  ("Satoshi Nagayasu / Uptime Technologies, LLC." <snaga@uptime.jp>)
Re: LWLOCK_STATS  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 07.01.2012 00:24, Robert Haas wrote:
> It's been a while since I did any testing with LWLOCK_STATS defined,
> so I thought it might be about time to do that again and see how
> things look.  Here's how they looked back in July:
>
> http://archives.postgresql.org/pgsql-hackers/2011-07/msg01373.php

Interesting.

A couple of weeks ago I wrote a little patch that's similar to 
LWLOCK_STATS, but it prints out % of wallclock time that is spent 
acquiring, releasing, or waiting for a lock. I find that more useful 
than the counters.

Here's the patch, I hope it's useful to others. It uses timer_create() 
and timer_settime(), so it probably won't work on all platforms, and 
requires linking with -lrt.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: broken link to PostgreSQL 9.1 repository for Fedora 14
Next
From: Heikki Linnakangas
Date:
Subject: Re: LWLOCK_STATS