From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Greg Smith <gsmith(at)gregsmith(dot)com> |
Subject: | Re: Performance Monitoring |
Date: | 2007-06-17 04:30:15 |
Message-ID: | 200706170030.16112.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Friday 15 June 2007 13:29, Greg Smith wrote:
> On Fri, 15 Jun 2007, Umar Farooq wrote:
> > Surprisingly, no matter what type of query I execute, when I use strace
> > to monitor the system calls generated they turn out to be the same for
> > ALL sorts of queries.
>
> How are you calling strace? The master postgres progress forks off new
> processes for each of the clients, you need to make sure you include stats
> from all of them as well to get anything.
>
> I normally use
>
> strace -c -f -p [main postgres process]
>
> which is helpful to collecte basic info, but even that's not quite right;
> you don't get the work done by the other proceses (logger, writer, stats
> collector). To get everything, you need to start some process that you
> attach strace to like this, then have that process start the server.
>
> I haven't found strace to be a great tool for this type of work. You
> might take at look at systemtap instead (
> http://sourceware.org/systemtap/wiki ) which is a bit immature but is
> going the right direction.
>
> I will now bow my head and wait for someone to suggest you move to an OS
> that supports dtrace.
>
You know that's what I was thinking :-)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2007-06-17 05:36:33 | Re: Load Distributed Checkpoints test results |
Previous Message | Bruce Momjian | 2007-06-17 04:00:58 | Updated tsearch documentation |