Re: mod_perl installed but not faster

Well off the top of my head, you're performing an HTTP fetch from another server which is most likely where all the time is spent so the overhead of forking a process and loading perl probably doesn't add up to much.

It's like driving behind a blue haired lady, It doesn't matter if you're in a Diablo or a Dart, you'll still be doing 15 MPH.

-Lee

"To be civilized is to deny one's nature."

Comment on Re: mod_perl installed but not faster

Replies are listed 'Best First'.
Re: Re: mod_perl installed but not faster by true (Pilgrim) on Oct 18, 2002 at 11:00 UTC
I specified in my node that Both scripts exist on the same server. I was hoping to test the speed of mod_perl as well as multiple requests through apache. that's why i did a simple fetch 10 times.	[reply]
Re: Re: Re: mod_perl installed but not faster by shotgunefx (Parson) on Oct 18, 2002 at 11:16 UTC
mod_perl with Apache::Registry is only saving you the compilation time (compiling source/loading modules). The compilation and execution of your script compared to the fetch (opening a socket, sending the request, connecting, waiting for the server to fork, starting perl, compiling, executing and sending response) is a relativly small amount of time. If index.cgi is a slow script then it just makes the comparison even more moot. A better benchmark might be a script that contains a large data structure, lots of modules or simple parses a CGI request and prints a response. -Lee "To be civilized is to deny one's nature."	[reply]