Re: testing ProcArrayLock patches - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: testing ProcArrayLock patches
Date
Msg-id 4EC668A10200002500043257@gw.wicourts.gov
Whole thread Raw
In response to Re: testing ProcArrayLock patches  (Andres Freund <andres@anarazel.de>)
Responses Re: testing ProcArrayLock patches
List pgsql-hackers
Andres Freund <andres@anarazel.de> wrote:
> When doing line-level profiles I would suggest looking at the
> instructions.
What's the best way to do that?
> I don't think cache line contention is the most likely candidate
> here.  Simple cache-misses seem far more likely. In combination
> with pipeline stalls...
> 
> Newer cpus (nehalem+) can measure stalled cycles which can be
> really useful when analyzing performance. I don't remember how to
> do that with oprofile right now though as I use perf these days
> (its -e stalled-cycles{frontend|backend} there}).
When I run oprofile, I still always go back to this post by Tom:
http://archives.postgresql.org/pgsql-performance/2009-06/msg00154.php
Can anyone provide such a "cheat sheet" for perf?  I could give that
a try if I knew how.
-Kevin


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: testing ProcArrayLock patches
Next
From: Andres Freund
Date:
Subject: [PATCH] Replace a long chain of if's in eval_const_expressions_mutator by a switch()