[Catalyst] How to share a database connection across multiple Catalyst apps?

Nicholas Wehr catalyst at bionikchickens.com
Wed Sep 8 03:40:59 GMT 2010

I'm with Tom on this one. Unless you've narrowed all optimization efforts
and this is all you have left - it could be worth a try.. but as Jason
points out, you may not gain a thing. I'd recommend profiling your code and
tracking down performance issues from that base level. Please post your
results - I've very curious!


On Tue, Sep 7, 2010 at 7:21 PM, Tomas Doran <bobtfish at bobtfish.net> wrote:

> On 7 Sep 2010, at 18:59, Simon Miner wrote:
>> All three of these apps run under a single Apache 1.3.42/mod_perl 1.31
>> server.
> Wow, mod_perl 1.... Ok then :)
>   It appears that each server process creates a unique database connection
>> variable for each of these apps. Although these database connections get
>> reused from request to request, I would like to make things even more
>> efficient by having a single database connection variable per server pro=
>> which gets shared across all 3 Catalyst apps.
> Why do you think that this will help or affect anything?
> I.e. is this not premature optimisation?
> Cheers
> t0m
> _______________________________________________
> List: Catalyst at lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20100907/02eba=

More information about the Catalyst mailing list