From: | Mike Nolan <nolan(at)gw(dot)tssi(dot)com> |
---|---|
To: | chris(dot)kratz(at)vistashare(dot)com (Chris Kratz) |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Long running queries degrade performance |
Date: | 2004-04-16 15:46:02 |
Message-ID: | 200404161546.i3GFk3p3010490@gw.tssi.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> We have a web app with a postgres backend. Most queries have subsecond
> response times through the web even with high usage. Every once in awhile
> someone will run either an ad-hoc query or some other long running db
> process.
Are you sure it is postgres where the delay is occurring? I ask this
because I also have a web-based front end to postgres, and while most of
the time the queries respond in about a second every now and then I see
one that takes much longer, sometimes 10-15 seconds.
I've seen this behavior on both my development system and on the
production server.
The same query a while later might respond quickly again.
I'm not sure where to look for the delay, either, and it is intermittent
enough that I'm not even sure what monitoring techniques to use.
--
Mike Nolan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-16 16:34:11 | Re: Horribly slow hash join |
Previous Message | Jim C. Nasby | 2004-04-16 15:45:02 | Horribly slow hash join |