harleypig has asked for the wisdom of the Perl Monks concerning the following question:

I'm testing DBD::ProxyServer with DBI::Proxy. I'm pretty sure that the proxy server is *not* caching the connections to the db. Am I correct? If so, what concerns should I have when modifying the AcceptUser sub to use connect_cached?

Harley J Pig
  • Comment on DBD ProxyServer Not Caching Connections

Replies are listed 'Best First'.
Re: DBD ProxyServer Not Caching Connections
by perrin (Chancellor) on Feb 17, 2006 at 00:32 UTC
    You're right, it doesn't cache connections. In general it has terrible performance and is a last resort. If you want to try caching connections, go for it, but make sure you don't try to use them across multiple processes, i.e. make sure they are opened after forking.
[reply]

      Thank you for that clarification.

      What I'm trying to figure out (I'm learning as I go, but I'm running out of time) is whether or not the following scenario is correct (or even a good idea):

      A cgi script on a bank of web boxes uses DBI->connect_cache to connect to a dbi proxy, which then uses DBI->connect_cache to a bank of db boxes.

      I can't find anything seems to do this, or similar. Thanks for the pointer.

      Harley J Pig
[reply]
        What you're suggesting sounds reasonable, but I think it will require more work than you expect. The proxy server is still likely to be slow after this change, compared to direct access.
[reply]

Back to Seekers of Perl Wisdom