Horton

Re: testing ProcArrayLock patches

Kevin Grittner <kevin.grittner@wicourts.gov>

View thread
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Andres Freund" <andres@anarazel.de>
Cc: "Robert Haas" <robertmhaas@gmail.com>, <pgsql-hackers@postgresql.org>
Date: 2011-11-18T20:16:01Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Don't elide blank lines when accumulating psql command history.

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