X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9A59FD1C9BE for ; Fri, 16 Apr 2004 17:25:17 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 63942-09 for ; Fri, 16 Apr 2004 17:25:12 -0300 (ADT) Received: from gw.tssi.com (gw.tssi.com [198.147.197.1]) by svr1.postgresql.org (Postfix) with ESMTP id 42430D1D6CC for ; Fri, 16 Apr 2004 17:25:13 -0300 (ADT) Received: from gw.tssi.com (nolan@gw.tssi.com [127.0.0.1] (may be forged)) by gw.tssi.com (8.12.6/8.12.6) with ESMTP id i3GKPE8S013712; Fri, 16 Apr 2004 15:25:14 -0500 Received: (from nolan@localhost) by gw.tssi.com (8.12.6/8.12.6/Submit) id i3GKPDe4013710; Fri, 16 Apr 2004 15:25:13 -0500 From: Mike Nolan Message-Id: <200404162025.i3GKPDe4013710@gw.tssi.com> Subject: Re: Long running queries degrade performance To: chris.kratz@vistashare.com (Chris Kratz) Date: Fri, 16 Apr 2004 15:25:12 -0500 (CDT) Cc: pgsql-performance@postgresql.org In-Reply-To: <200404161356.20210.chris.kratz@vistashare.com> from "Chris Kratz" at Apr 16, 2004 01:56:20 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/225 X-Sequence-Number: 6525 > Fairly sure, when it is happening, postgres usually is taking up the top slots > for cpu usage as reported by top. Perhaps there is a better way to monitor > this? Given the intermittent nature of the problem and its relative brevity (5-10 seconds), I don't know whether top offers the granularity needed to locate the bottleneck. > likely you have a situation where something else is happening which blocks > the current thread. It happens on my development system, and I'm the only one on it. I know I've seen it on the production server, but I think it is a bit more common on the development server, though that may be a case of which system I spend the most time on. (Also, the production server is 1300 miles away with a DSL connection, so I may just be seeing network delays some of the time there.) > Both of these were triggered by users double clicking links in our > web app and were fixed by a better implementation. Perhaps something like > that is causing what you are seeing. My web app traps double-clicks in javascript and ignores all but the first one. That's because some of the users have mice that give double-clicks even when they only want one click. -- Mike Nolan