On Tue, Nov 13, 2001 at 09:18:04PM -0500, Perrin Harkins wrote:
One run of my script takes about 2 seconds. This includes a lot of
database-queries, calculations and so on. about 0.3 seconds are used
just for one command: $query=new CGI;
That's really awfully slow. Are you positive
Check out the docs at:
http://stein.cshl.org/WWW/software/CGI/#mod_perl
There's specific notes on how to make CGI.pm play nicely with mod_perl.
--
===
If you put three drops of poison into a 100 percent pure Java, you
On Wed, Nov 14, 2001 at 10:39:36AM -0500, Perrin Harkins wrote:
its definitely running under mod_perl. But imho the time it takes to
create a new cgi-object should not depend too much wheter its running
under mod_perl or not, cause the CGI-module is loaded before. (In fact
I load in
If it was running under CGI, it would be compiling CGI.pm on each
request,
which I've seen take .3 seconds. Taking that long just to create the
new
CGI instance seems unusual. How did you time it? Are you using
Apache::DProf?
Wouldnt it be compiled at the use-statement ?
Yes, but
That's usually pretty accurate, so I guess it really takes
that long on your system. Try Apache::Request! Or even one
of the lighter CGI modules like CGI_Lite.
in my case it means up to 4 connections per process, cause
in fact it
is not one module but 2 (input and output) and each
One of the reasons you should probably not have a persistent/global CGI
object is that
upon a new the CGI module reads in numerous environment variables and
setups up its
internal structures for that particular query. If $q (in $q=new CGI) was
persistent/global
you would possibly have the wrong
One run of my script takes about 2 seconds. This includes a lot of
database-queries, calculations and so on. about 0.3 seconds are used
just for one command: $query=new CGI;
That's really awfully slow. Are you positive it's running under mod_perl?
Have you considered using Apache::Request