Quoting Bob Foster <[EMAIL PROTECTED]>:
> Immediately
> after I make an Oracle database connection, the child jumps from a size
> of
> 3.6M (2.4M shared) to 17.4M (3.4M shared). The child process slowly
> grows
> to 22.2M (3.4M shared). The loaded libs Sizes total 13.6M.
>
> Shouldn't the libs
Quoting Joshua Chamas <[EMAIL PROTECTED]>:
> Also, more a side note, I have found that you have to fully
> restart apache, not just a graceful, if either the Oracle server
> is restarted or the TNS listener is restarted.
We fixed this at eToys by having children that failed to connect to the
dat
Bob Foster wrote:
>
> Thank you very much, Joshua. I have made some progress and am now seeing
> 15.8M shared out of 16.7M on the parent. I believe that the problem was
> that I was doing a graceful restart which wasn't restarting the parent
> process.
>
> Now I have a different problem. When
[EMAIL PROTECTED] writes:
>
>Make sure to "use DBD::Oracle" in your startup.pl or
>do PerlModule DBD::Oracle ... that should load up some
>Oracle libs in the parent. Also, you *might* try
>doing a connect or even an invalid connect to Oracle,
>which might grab some extra libs that it only loads
>
Bob Foster wrote:
>
> Hi,
>
> I'm using Stas Bekman's excellent Apache::VMonitor module to help me
> decrease my mod_perl child process memory usage. I was working on
> preloading all of my perl modules and scripts in a startup.pl script when
> I noticed that the amount of shared memory seemed
Hi,
I'm using Stas Bekman's excellent Apache::VMonitor module to help me
decrease my mod_perl child process memory usage. I was working on
preloading all of my perl modules and scripts in a startup.pl script when
I noticed that the amount of shared memory seemed very low. Immediately
after I ma
