OT: Measuring CPU time use? (Another stupid question)

Oh, I meant "Visual". Just had one too many neurons misfire... :)

On Wed, 18 Dec 2002, scott.marlowe wrote:

> Actually, I'd be more bothered by the "Visual" in the name :-)
>
> Just because it comes from RedHat doesn't mean it's shite. Some of their
> stuff is quite nice. Just use the 'explain' or 'explain analyze' sql
> statement, it'll get you what you need. But, pay attention to the CPU/IO
> usage, as that will tell you what your limiting factors are.
>
> On Wed, 18 Dec 2002, Jessica Blank wrote:
>
> > Bllllleleeeuuuughhh...
> >
> > I'd rather not touch Red Hat's stuff.. or ANYTHING with "Explain" in the
> > name >G< Thank you for the info tho...
> >
> > I would much rather just get the info via a simple command line, or a line
> > of SQL, or something I can do in Perl....
> >
> > On Thu, 19 Dec 2002, Justin Clift wrote:
> >
> > > Joe Conway wrote:
> > > > Jessica Blank wrote:
> > > >
> > > >> I suppose I should rephrase.
> > > > [...snip...]
> > > >> So I guess what I'm saying is that I don't care so much about CPU
> > > >> time, or I/O time, but *TOTAL* time. How long it takes from the
> > > >> instant the query hits Postgres to the instant I get my results back...
> > > >
> > > >
> > > > That's pretty much exactly what EXPLAIN ANALYZE does for you. And along
> > > > with it, you get other useful information to help you improve the query.
> > >
> > > Red Hat recently released their "Visual Explain 1.1" tool as well, and that looks like it could be very useful for what
> > > Jessica's after too:
> > >
> > > http://sources.redhat.com/rhdb/tools.html
> > >
> > > :-)
> > >
> > > Regards and best wishes,
> > >
> > > Justin Clift
> > >
> > >
> > > > Joe
> > >
> > >
> > >
> > >
> >
> >
>

--
J e s s i c a L e a h B l a n k