From: | Jan Urbański <wulczer(at)wulczer(dot)org> |
---|---|
To: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pgbench--new transaction type |
Date: | 2011-06-13 08:48:39 |
Message-ID: | 4DF5CEE7.3030500@wulczer.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13/06/11 06:38, Greg Smith wrote:
> On 06/11/2011 03:21 PM, Jeff Janes wrote:
>> I wouldn't expect IPC chatter to show up in profiling, because it
>> costs wall time, but not CPU time. The time spent might be attributed
>> to the kernel, or to pgbench, or to nothing at all.
>>
>
> Profilers aren't necessarily just accumulating raw CPU time though. If
> the approach includes sampling "what code is active right now?"
> periodically, you might be able to separate this out even though it's
> not using CPU time in the normal fashion. I think you might just need
> to use a better profiler.
I got surprisingly insightful results in the past using
http://poormansprofiler.org/
I never used it with Postgres, but it might be worth to try.
J
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei KaiGai | 2011-06-13 11:51:55 | Re: [v9.1] sepgsql - userspace access vector cache |
Previous Message | Jaime Casanova | 2011-06-13 08:39:39 | Re: DOMAINs and CASTs |