Horton

Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile

Sergey Koposov <koposov@ast.cam.ac.uk>

View thread
From: Sergey Koposov <koposov@ast.cam.ac.uk>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jeff Janes <jeff.janes@gmail.com>, Florian Pflug <fgp@phlo.org>, Merlin Moncure <mmoncure@gmail.com>, pgsql-hackers@postgresql.org, Stephen Frost <sfrost@snowman.net>
Date: 2012-05-31T11:31:56Z
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. Improve bulk-insert performance by keeping the current target buffer pinned

Attachments

Hi,

On Wed, 30 May 2012, Robert Haas wrote:

> I'd really like to find out exactly where all those s_lock calls are
> coming from.  Is there any way you can get oprofile to output a
> partial stack backtrace?  If you have perf it's very easy, just 'perf
> record -g -a <command to launch your test case>' and then 'perf report
> -g'.

I repeated my test with 8 threads (without tasksetting) and with 
sharedbuffers=48g (because that seemed to trigger in particular long 
times ~ 80 seconds). And I attach the perf report.

Cheers,
 	S

*****************************************************
Sergey E. Koposov, PhD, Research Associate
Institute of Astronomy, University of Cambridge
Madingley road, CB3 0HA, Cambridge, UK
Tel: +44-1223-337-551 Web: http://www.ast.cam.ac.uk/~koposov/