Fwd: RE: [imp] DB Connection Handle Consumption

[Chuck Hagenbuch]

----- Forwarded message from "Sexton, George" <gsexton@mhsoftware.com> ----
-
    Date: Sun, 21 Apr 2002 21:58:30 -0600
    From: "Sexton, George" <gsexton@mhsoftware.com>
Reply-To: "Sexton, George" <gsexton@mhsoftware.com>
 Subject: RE: [imp] DB Connection Handle Consumption
      To: Chuck Hagenbuch <chuck@horde.org>

OK, I found the setting in PHP.INI to limit it to a reasonable value. I am
curious though. In another thread that discussed this, you talked about not
caching database connections and the performance hit. I know from 
experience
that this can be pretty expensive. The way I get around it in servlet
development is to use a connection pooling class.

What I don't understand is why IMP sets up and tears down the IMAP
connection on every page view. Surely this is a big performance problem
spawning a new imapd every time the user clicks on something. Is there a 
way
to turn this on?



-----Original Message-----
From: Chuck Hagenbuch [mailto:chuck@horde.org]
Sent: 21 April, 2002 9:47 PM
To: Sexton, George
Cc: imp@lists.horde.org
Subject: Re: [imp] DB Connection Handle Consumption


Quoting "Sexton, George" <gsexton@mhsoftware.com>:

> I have noticed that Horde seems to be establishing database connection
> handles and a) not freeing them, and b) not re-using them.

Horde uses the PEAR DB layer, and by default we use persistent
connections. If you're using Apache, that means you get one database
connection held open per apache child. If you have many moren apache
children than allowed database connections, you'll have problems.

-chuck

--
Charles Hagenbuch, <chuck@horde.org>
"A dream which helps you to live your reality with dignity
 and justice is a good dream." - Tariq Ramadan

----- End forwarded message -----


-chuck

--
Charles Hagenbuch, <chuck@horde.org>
"A dream which helps you to live your reality with dignity
 and justice is a good dream." - Tariq Ramadan