Skip site navigation (1) Skip section navigation (2)

Re: GiST index performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matthew Wakeling <matthew(at)flymine(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: GiST index performance
Date: 2009-06-10 16:51:31
Message-ID: 7684.1244652691@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Matthew Wakeling <matthew(at)flymine(dot)org> writes:
> The final cumulative time is 5894.06 seconds, which doesn't seem to match 
> the query run time at all.

Depending on the platform you're using, gprof might have the wrong idea
about the kernel's tick rate, leading to its numbers being some multiple
or fraction of the true elapsed time.  I had that problem awhile back
https://bugzilla.redhat.com/show_bug.cgi?id=151763
although I'd like to think it's fixed on all recent Linuxen.  However,
your bigger problem is here:

> Also, no calls to anything including "bioseg" 
> in the name are recorded, although they are definitely called as the GiST 
> support functions for that data type.

I have never had any success in getting gprof to profile functions that
are in loadable libraries, which of course is exactly what you need to do
here.  I have found hints on the web claiming that it's possible, but
they don't work for me.  gprof just ignores both the functions and the
time spent in them.

Personally I generally use oprofile these days, because it doesn't have
that problem and also doesn't require any special build options.  If you
don't have that available to you, the best bet is probably to make a
test build of Postgres in which your functions are linked directly into
the main postgres executable.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2009-06-10 17:07:06
Subject: Re: Why is my stats collector so busy?
Previous:From: Kevin GrittnerDate: 2009-06-10 16:40:21
Subject: Re: Looking for installations with a large number of concurrent users

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group