in reply to Re: PHP is better than perl and what can i do to run perl faster?
in thread PHP is better than perl and what can i do to run perl faster?

"When Perl is run as a webserver module, one instance of the interpreter is started with the webserver and multiple threads of execution are used"

Correct me if I'm wrong but with mod_perl (Apache), we have one instance of the Perl interpreter for each thread/process of the WebServer, and not the apposite.

We also doesn't have memory cache of "pages", unless this is implemented over a embeded html system, like HTML::Mason. What we have is that for each execution of a mod_perl module we are just continuing the execution of the module, so, is like to have a script that doesn't die and only need to be parsed and started 1 time, what is much more faster.

Graciliano M. P.
"Creativity is the expression of the liberty".

  • Comment on Re^2: PHP is better than perl and what can i do to run perl faster?

Replies are listed 'Best First'.
Re^3: PHP is better than perl and what can i do to run perl faster?
by adrianh (Chancellor) on Jun 14, 2004 at 07:49 UTC

    "When Perl is run as a webserver module, one instance of the interpreter is started with the webserver and multiple threads of execution are used"

    Correct me if I'm wrong but with mod_perl (Apache), we have one instance of the Perl interpreter for each thread/process of the WebServer, and not the apposite.

    The key word is "started". While each mod_perl process has their own copy of the perl interpreter you only suffer the time expense of starting up perl and loading modules the one time. After that it's just cheap forks.