pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Effects of IDLE processes
5+ messages / 4 participants
[nested] [flat]

* Effects of IDLE processes
@ 2005-02-18 10:15  JM <jerome@gmanmi.tv>
  0 siblings, 2 replies; 5+ messages in thread

From: JM @ 2005-02-18 10:15 UTC (permalink / raw)
  To: pgsql-performance

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


TIA,




^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Effects of IDLE processes
@ 2005-02-18 14:16  Tom Lane <tgl@sss.pgh.pa.us>
  parent: JM <jerome@gmanmi.tv>
  1 sibling, 0 replies; 5+ messages in thread

From: Tom Lane @ 2005-02-18 14:16 UTC (permalink / raw)
  To: jerome@gmanmi.tv; +Cc: pgsql-performance

JM <jerome@gmanmi.tv> writes:
> 	I was wondering if there is a DB performance reduction if there are a lot of 
> IDLE processes.

There will be some overhead, but I dunno if anyone's ever tried to
measure it.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Effects of IDLE processes
@ 2005-02-21 00:50  Gaetano Mendola <mendola@bigfoot.com>
  parent: JM <jerome@gmanmi.tv>
  1 sibling, 1 reply; 5+ messages in thread

From: Gaetano Mendola @ 2005-02-21 00:50 UTC (permalink / raw)
  To: JM <jerome@gmanmi.tv>

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 @#$


Regards
Gaetano Mendola





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Effects of IDLE processes
@ 2005-02-21 03:18  Christopher Browne <cbbrowne@acm.org>
  parent: Gaetano Mendola <mendola@bigfoot.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Christopher Browne @ 2005-02-21 03:18 UTC (permalink / raw)
  To: pgsql-performance

After a long battle with technology, Gaetano Mendola <mendola@bigfoot.com>, 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.

"idle in transaction" is quite another matter; long-running
transactions certainly do lead to evil.  When running Slony-I, for
instance, "idle in transaction" means that pg_listener entries are
being held onto so they cannot be vacuumed out, and that's only one
example of a possible evil...
-- 
(reverse (concatenate 'string "moc.liamg" "@" "enworbbc"))
http://linuxdatabases.info/info/languages.html
You know  how most packages say  "Open here". What is  the protocol if
the package says, "Open somewhere else"?



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Effects of IDLE processes
@ 2005-02-21 11:23  Gaetano Mendola <mendola@bigfoot.com>
  parent: Christopher Browne <cbbrowne@acm.org>
  0 siblings, 0 replies; 5+ messages in thread

From: Gaetano Mendola @ 2005-02-21 11:23 UTC (permalink / raw)
  To: Christopher Browne <cbbrowne@acm.org>

Christopher Browne wrote:
> After a long battle with technology, Gaetano Mendola <mendola@bigfoot.com>, 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






^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2005-02-21 11:23 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-02-18 10:15 Effects of IDLE processes JM <jerome@gmanmi.tv>
2005-02-18 14:16 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-02-21 00:50 ` Gaetano Mendola <mendola@bigfoot.com>
2005-02-21 03:18   ` Christopher Browne <cbbrowne@acm.org>
2005-02-21 11:23     ` Gaetano Mendola <mendola@bigfoot.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox