Re: measuring spinning - Mailing list pgsql-hackers

From Robert Haas
Subject Re: measuring spinning
Date
Msg-id CA+TgmobJECocmVbQ-O0aEzhPkXNUUxPDYxM9KgL+D0ZocRcXTg@mail.gmail.com
Whole thread Raw
In response to measuring spinning  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: measuring spinning
Re: measuring spinning
List pgsql-hackers
On Wed, Jan 11, 2012 at 8:48 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> I've had cause, a few times this development cycle, to want to measure
> the amount of spinning on each lwlock in the system.  To that end,
> I've found the attached patch useful.  Note that if you don't define
> LWLOCK_STATS, this changes nothing except that the return value from
> s_lock becomes int rather than void.  If you do define LWLOCK_STATS,
> then LWLockAcquire() counts the number of pg_usleep() calls that are
> required to acquire each LWLock, in addition to the other statistics.
> Since this has come up for me a few times now, I'd like to proposing
> including it in core.

Well, this fell through the cracks, because I forgot to add it to the
January CommitFest.  Here it is again, rebased.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH 06/16] Add support for a generic wal reading facility dubbed XLogReader
Next
From: Andres Freund
Date:
Subject: Re: [PATCH 06/16] Add support for a generic wal reading facility dubbed XLogReader