X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D1EC58BA91F for ; Mon, 21 Feb 2005 11:25:25 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23476-10 for ; Mon, 21 Feb 2005 11:25:19 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5A5038B9F77 for ; Mon, 21 Feb 2005 11:25:21 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 4BB2B31FE9; Mon, 21 Feb 2005 12:25:21 +0100 (MET) From: Gaetano Mendola X-Newsgroups: pgsql.performance Subject: Re: Effects of IDLE processes Date: Mon, 21 Feb 2005 12:23:15 +0100 Organization: Hub.Org Networking Services Lines: 51 Message-ID: <4219C4A3.20100@bigfoot.com> References: <200502181815.17000.jerome@gmanmi.tv> <4219304A.1070408@bigfoot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org To: Christopher Browne User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en In-Reply-To: X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/284 X-Sequence-Number: 10613 Christopher Browne wrote: > After a long battle with technology, Gaetano Mendola , an earthling, wrote: > >>JM wrote: >> >>>Hi ALL, >>> >>> I was wondering if there is a DB performance reduction if >>>there are a lot of IDLE processes. >>> >>>30786 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>>32504 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>>32596 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 1722 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 1724 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 3881 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 6332 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 6678 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 6700 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 6768 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 8544 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 8873 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 8986 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 9000 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 9010 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 9013 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 9016 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 9019 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> 9020 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >>> > > >>In my experience not at all, you have to wonder if some of that are >>"idle in transaction" that are really a pain in the @#$ > > > I'd be concerned about "idle" processes insofar as they are holding on > to _some_ memory that isn't shared. For "not at all" I was refering the fact that the normal engine work and maintenances are not affected ( at least your iron shall be able to support all these connections and processes ). A long transaction for example can stop the entire engine if for example a "Vacuum full" remain stuck on some tables locked by that transaction Regards Gaetano Mendola