> I believe top's percent-of-CPU numbers for individual
> processes are time
> averages over a minute or so, so the ramping effect is
> unsurprising.
Thanks - this makes much more sense.
> > This doesn't really tell me much, except I'm guessing that
> > PG is CPU bound?
>
> Yup, that seems pretty clear. Next step is to find out what
> the heck
> it's doing. My instinct would be to use gprof. Recompile
> with
> profiling enabled --- if you're using gcc, this should work
> cd postgres-distribution/src/backend
> make clean
> make PROFILE=-pg all
> make install-bin -- may need to stop postmaster
> Next run some sample queries (put them all into one session).
> After quitting the session, find gmon.out in the
> $PGDATA/base/nnn/ subdirectory corresponding to your database,
> and feed it to gprof.
> The results should show where the code hotspot is.
Well if that isn't a fancy bit of info.... Thanks!
gprof says:
Fatal ELF error: can't read ehdr (Request error: class
file/memory mismatch)
I'm guessing that's not what we're expecting... I'm using
/usr/ccs/bin/gprof - maybe there's a better one?
-X
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com