testing server response time

2002-01-10 Thread Alan Raetz
I was trying to test the CGI response time of a Perl/CGI script under two conditions: as multiple modules versus a single big script. First I installed IndigoPerl (from indigostar.com) on my Windows machine (which has an integrated apache server with mod_perl enabled by default). Then I ran this

Re: testing server response time

2002-01-10 Thread Perrin Harkins
After I set up my app (webtool.cgi) and created the single script version (bigtool.cgi), I ran this script on my machine and it showed that the single file was about 10-15% faster than the multiple modules. No offense, but your script must not have been doing much in this test. The

Re: testing server response time

2002-01-10 Thread Alan Raetz
Perrin, Thanks for the response, --- Perrin Harkins [EMAIL PROTECTED] wrote: No offense, but your script must not have been doing much in this test. The difference between putting everything in one script vs. using modules is just the time it takes to open and read the files. It's a

Re: testing server response time

2002-01-10 Thread Perrin Harkins
I was also thinking it would only make a small difference, but I see many perl/CGI scripts that boast 'all this functionality in a single script' They probably don't know any better, but to me that translates to giant bloated unorganized mess of a script. # BEGIN MOD_PERL CONFIG

Re: testing server response time

2002-01-10 Thread Alan Raetz
Perrin, You want something more like this: Alias /perl-bin/ c:/IndigoPerl//perl-bin/ PerlModule Apache::Registry Location /perl-bin SetHandler perl-script PerlHandler Apache::Registry Options ExecCGI /Location Yup, this gets it working (It does need the line LoadModule