From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: pgsql-performance@postgresql.org
Subject: Re: SSI slows down over time
Date: Mon, 07 Apr 2014 06:52:54 -0400
Message-ID: <53428386.6040607@cs.utoronto.ca> (raw)
In-Reply-To: <534110B6.8020509@vmware.com>
References: <5340BB09.5010101@cs.utoronto.ca>
<534110B6.8020509@vmware.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 06/04/2014 4:30 AM, Heikki Linnakangas wrote:
> On 04/06/2014 05:25 AM, Ryan Johnson wrote:
>> I've tried linux perf, but all it says is that lots of time is going to
>> LWLock (but callgraph tracing doesn't work in my not-bleeding-edge
>> kernel).
>
> Make sure you compile with the "-fno-omit-frame-pointer" flag.
Oh, right. Forgot about that. With -g in place, it shows 5% of time
going to LWLockAcquire, virtually all of that in PredicateLockPage.
However, top reports only 50% utilization, so I'd *really* like to have
stack traces and "counts" for stack traces the worker thread spends its
time blocked in. I don't know a way to get that out of perf, though.
It's near-trivial to do in dtrace, but unfortunately I don't have a
Solaris or BSD machine handy.
Does pgsql give a way to trace latencies due to LWLock?
Thanks,
Ryan
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ryan.johnson@cs.utoronto.ca
Subject: Re: SSI slows down over time
In-Reply-To: <53428386.6040607@cs.utoronto.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox