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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers