> "Wim" == Wim Kerkhoff <[EMAIL PROTECTED]> writes:
Wim> We're using SqlNet to connect multiple Linux web servers to
Wim> Oracle running on a Solaris box.
Adjust 'processes' and 'sessions' upwards in your init.ora file
on your database server.
Use:
svrmgrl
connect inernal
show param
At 11:04 AM 5/9/00, Wim Kerkhoff wrote:
>Snip [...]
Hmmm. Well, some things to look at:
globals aren't too good (i.e. use vars qw(...) ). Best to "localize" with my();
What's the SQL statement look like?
$sth->fetchrow returns an array but I don't know off the top of my head if
it automagic
>
> Is doing the things below terribly bad? We're actually doing 90% of the
> stuff in embperl, but we ran into problems in scoping when using
> my (), so we
> switched to use vars.
>
> #!/usr/bin/perl -w
>
> # some sample code
> use strict;
> use MyStuff;
> use vars qw ($dbh $foo $bar $sql $sth
I don't think you want to "use vars" for your regular variables. Too
dangerous, and you set yourself up for memory leaks. Declare them as
lexicals. Only use a global for something you want to cache ($dbh).
Something like:
#!/usr/bin/perl -w
# some sample code
use strict;
On Tue, 9 May 2000, Wim Kerkhoff wrote:
> On 09-May-2000 Perrin Harkins wrote:
> > On Mon, 8 May 2000, Wim Kerkhoff wrote:
> >> On a fresh restart of apache, my processes are about 20 ~ 25 MB each,
> >> which is about normal for mod_perl (as far as I know). However,
> >> within a few hours (with
Hmm, I may give that a try.
My main issue was all the memory it was taking 10 mod_perl process taking
up 512+ MB of memory is just not right.
I was thinking that they way I was passing the database handle $dbh between
functions was actually making a copy of the connection instead of a point
On 08-May-2000 Jeff Beard wrote:
> Not strange, a memory leak. You've got some bad code. If you have a program
> that you've been twiddling with recently, that would be the place to start
> looking.
The thing is, It's been doing this since I started coding on things...
I just clicked into a
On 09-May-2000 Perrin Harkins wrote:
> On Mon, 8 May 2000, Wim Kerkhoff wrote:
>> On a fresh restart of apache, my processes are about 20 ~ 25 MB each,
>> which is about normal for mod_perl (as far as I know). However,
>> within a few hours (with little use except by our development team),
>> th
> You're probably doing something that is causing certain variables to have
> temporarily large values. As always, start with the guide:
>
> http://perl.apache.org/guide/performance.html#Memory_leakage
>
> You should also make sure you're doing the usual pre-loading and other
> suggestions fro
On Mon, 8 May 2000, Wim Kerkhoff wrote:
> On a fresh restart of apache, my processes are about 20 ~ 25 MB each,
> which is about normal for mod_perl (as far as I know). However,
> within a few hours (with little use except by our development team),
> the size is up to 40MB, and by the end of the
Not strange, a memory leak. You've got some bad code. If you have a program
that you've been twiddling with recently, that would be the place to start
looking.
--Jeff
At 09:34 AM 5/8/00, Wim Kerkhoff wrote:
>I'm running into something kind of strange...
>
>On a fresh restart of apache, my proc
On 08-May-2000 [EMAIL PROTECTED] wrote:
> I AM NOT AN EXPERT. Which is why I didn't post to the list.
> I just happened to notice your question, and since everyone
> seems to be out to lunch, I though I'd give it a whack.
Thanks... I'm a quite new to mod_perl as well, and on some of the things I
I'm running into something kind of strange...
On a fresh restart of apache, my processes are about 20 ~ 25 MB each, which is
about normal for mod_perl (as far as I know). However, within a few hours
(with little use except by our development team), the size is up to 40MB, and
by the end of the d
13 matches
Mail list logo
