> I had written a database pool last year which got around this problem by > keeping track of the last time the connection was released. Then the > ping was only made if that time was greater than 5 seconds. This made a > big difference by cutting the pings down to nil when the application is > heavily loaded. The thinking is that when the queries are spaced close > together, the fact that the previous query was successful gives the same > information as the ping would, so it is not necessary.
I would have thought that pinging the connection when it was idle would be preferable to pinging it just before it was needed (when you have less time to create a new one), and if it is busy then that is the best time to reduce unnecessary traffic. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
