John Saylor wrote:
>> and mod_perl is a lot more resource intensive than CGI
>
> i find this very difficult to believe. do you have any references/data
> that support this point? everything i've ever read and/or done myself
> has pointed out that mod_perl uses far *fewer* resources than CGI.
>
> that's why people use it.
The main difference is that in mod_perl you typically load every module that
your application might use upfront to avoid the runtime cost of loading it
later. It also gives you some memory savings on systems that support COW memory.
This can cause you to actually use more total memory since normal CGI programs
give back all their memory after each request. Most people do try to unload some
things to other, simpler proxy servers (static files, auth if you can do it in a
C module, etc) since they will be lighter and not as memory intensive.
Even if you do have memory problems you can always use something like
Apache::SizeLimit to control those.
Another factor to consider is database connections. If you're using Apache::DBI
(which most people do) you will have persistant connections associated with each
apache child. This means if you serve non-database related content with that
apache process you're still tying up a database handle.
Even with all this, I'd have to see some real numbers (time and memory usage) to
be convinced that file uploads will be cheaper with CGI than with mod_perl.
Especially if you put a simple proxy server in front.
--
Michael Peters
Developer
Plus Three, LP
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.