Greetings,

The problem is that the script takes more than 3 or 4 seconds to execute
sometimes.

So we have a script that takes 3-4 seconds to execute, each varaiable is
defined with my $var. and when the script ends it resets the value of the
variables using undef.

If multiple users execute the script within those 3-4 seconds will the
variables still be shared between them?

What would be the best way to avoid this ?

Thank you all for the quick answers and great information.

----- Original Message -----
From: "Tom Schindl" <[EMAIL PROTECTED]>
To: "Stas Bekman" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, September 22, 2004 3:59 PM
Subject: Re: Variables in memory.


> Stas Bekman wrote:
>
> > Tom Schindl wrote:
> >
> >> Thanks Stas for the full explaination. Indeed I didn't know exactly
> >> what's really going on behind the scences. Thanks for your
> >> explaination I'm always learning something new when reading your
> >> answers.
> >
> >
> > Thanks :)
> >
> >> Still on the one hand I recognize what you're trying to tell me, on
> >> the other hand could you give me more information about how things
> >> like this could be accomplished or better the other wayround how
> >> could I prevent things like 1 thread with 10 perl-interpreters and
> >> vice versa if I don't want it?
> >
> >
> > You use interpreter pool size control directives:
> >
http://perl.apache.org/docs/2.0/user/config/config.html#Threads_Mode_Specifi
c_Directives
> >
> >
> > You don't need to prevent anything. It's just that if your server uses
> > very little modperl and mostly doing static requests, you can have
> > just a few perl interpreters around (in the threaded mpm) and many
> > more threads. The above link explains how to set a limit on the size
> > of the pool.
> >
> > I know we need to write some docs explaining the nuances, since I've
> > done this more than once here on the list. But all that after mp2 is
> > released.
> >
> Oh. I see great. I dive into it when I have more time and I'm sure I'll
> come up with some "silly" questions, be prepared.
>
> --
> Report problems: http://perl.apache.org/bugs/
> Mail list info: http://perl.apache.org/maillist/modperl.html
> List etiquette: http://perl.apache.org/maillist/email-etiquette.html


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to