| From: | Sergey Koposov <koposov(at)ast(dot)cam(dot)ac(dot)uk> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Florian Pflug <fgp(at)phlo(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: 9.2beta1, parallel queries, ReleasePredicateLocks, CheckForSerializableConflictIn in the oprofile |
| Date: | 2012-05-31 11:31:56 |
| Message-ID: | alpine.LRH.2.02.1205311225180.6351@calx046.ast.cam.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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/
| Attachment | Content-Type | Size |
|---|---|---|
| rep1.out | text/plain | 616.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2012-05-31 11:32:29 | Re: heap_form_tuple crashing |
| Previous Message | Peter Geoghegan | 2012-05-31 11:16:38 | Re: Uh, I change my mind about commit_delay + commit_siblings (sort of) |