Re: Performance ?'s regarding Apache::Request

[Doug MacEachern]

On Thu, 20 Jan 2000, Clifford Lang wrote:

 mod_perl 1.21
 Apache 1.3.9
 Solaris 2.5.1, Linux 6.0
 
 Is this a good or bad idea?
 
 I want to create an inheritable module based on Apache::Request mainly for
 uploading files, then create individual PerlHandler modules for individual
 page content.
 
 If I do this, will the uploaded files end up increase the memory consumption
 of the module, or is all memory freed after the fileupload process?

Apache::Request reads the uploaded file in 4K chunks and saves it to a
tmpfile, just as CGI.pm does.  you shouldn't see the process grow to the
size of the file unless you've hit a bug we don't know about.

Performance ?'s regarding Apache::Request

[Clifford Lang]

mod_perl 1.21
Apache 1.3.9
Solaris 2.5.1, Linux 6.0

Is this a good or bad idea?

I want to create an inheritable module based on Apache::Request mainly for
uploading files, then create individual PerlHandler modules for individual
page content.

If I do this, will the uploaded files end up increase the memory consumption
of the module, or is all memory freed after the fileupload process?

I was going to use "register_cleanup(\CGI::_reset_globals)" to clear the
CGI environment but don't know if that frees up the memory.  If used, should
the register_cleanup be attached to the original request object ($r =
shift;), or the $apr=Apache::Request-new($r) object?

Should I (How can I) destroy the entire page after each request?  Doing so
would lose some of the reason for using mod_perl, I'd like to write these
handlers with all dynamic content (no "real" page source).  Some thoughts
for destruction would be to create the Apache::Request::Upload as a blessed
object, then destroy it on page completion - Is this wise or even possible?
Any pointers on how to accomplish this?


TIA,  Cliff