From: Chris W. <ch...@cw...> - 2003-10-29 16:34:38
|
Igor Vylusko wrote: > I have compared httpd size of two OI2 usage variants. > 1. OI2 starts as Apache::Registry cgi script. > 2. OI2 configured as handler. > > In second variant size of httpd process is 15M greater then first one. > > Why so valuable size difference? > I would like to use OI as handler, but memory limits of my ISP not > allow it. Is there some work around to have the same httpd size (as on > usage OI2 over Apache::Registry script) using OI2 as handler? When you say 'Apache::Registry' script, are you using the 'oi2.cgi' script that comes along with your website? If so, that's very interesting -- I've never tried that :-) Since the oi2.cgi script and the handler use the same modules I don't think that would be the problem. I assume you're still using the: PerlRequire /path/to/mysite/conf/startup.pl which does most of the necessary 'use' and 'require' at server startup time. That should do the same work for both Apache::Registry and using the handler. So I would guess the difference occurs because the handler stores additional data between requests -- oi2.cgi recreates the context object every time the script is called. Although since it's storing the singleton Context object in a class variable it might be maintained across requests... Honestly, I've only used Apache::Registry to run a TWiki site so I'm not sure what all the tips and tricks are, what it does behind the scenes, etc. I think there are Apache:: modules you can use to peek into what objects are stored between requests, how big they are, etc. That would probably be your next step. Hope that makes sense, Chris -- Chris Winters (ch...@cw...) Building enterprise-capable snack solutions since 1988. |