Saar Picker <[EMAIL PROTECTED]> writes:
> Thanks for responding. We currently are cacheing DB connections
> per-process. However, with 40-50 processes per server, and 4+ machines per
> DB server, and 3-5 connections per process, you can see how the number of
> connections per DB server gets rath
On Tue, 8 Feb 2000, Saar Picker wrote:
> Thanks for responding. We currently are cacheing DB connections
> per-process. However, with 40-50 processes per server, and 4+ machines per
> DB server, and 3-5 connections per process, you can see how the number of
> connections per DB server gets rather
Thanks for responding. We currently are cacheing DB connections
per-process. However, with 40-50 processes per server, and 4+ machines per
DB server, and 3-5 connections per process, you can see how the number of
connections per DB server gets rather large. I think the problem lies
with the CODE
On Tue, 8 Feb 2000, Saar Picker wrote:
> I've been trying cache DBI database handles using IPC::Shareable and
> IPC::Cache(based on ShareLite) without much luck. This is not necessarily
> a mod-perl problem, but I figured someone on this list must have tried
> this already.
Hi Saar -- sorry I ha
Hi all,
I've been trying cache DBI database handles using IPC::Shareable and
IPC::Cache(based on ShareLite) without much luck. This is not necessarily
a mod-perl problem, but I figured someone on this list must have tried
this already.
With either module, I get the following error message:
[Tu
