On Thursday 31 January 2002 05:36, [EMAIL PROTECTED] wrote: > My problem involves memory management between mod_perl processes. > I am running AxKit 1.5, with PerForm and the *new* session taglib. > I am using the Tangram framework for OO<->rdbms interface. This library > keeps cached versions of the db objects in memory.
Well that can fail or succeed, it depends on the cache checking code. However keeping stuff in memory in modperl is usually a bad idea. > If I limit apache to one process, forms under PerForm stop working (why?). That's a strange behaviour. I suggest that you submit a bug report to the author on http://rt.cpan.org. > If I don't limit, accessing an AxKit page starts at least one additional > apache process, so that I have at least two. Why ? Is this because AxKit is > large ? No, that's the normal way for Apache to work. I suggest that you read some minimal information on Apache and modperl (http://perl.apache.org/) to understand what's going on. > I tried to take AxKit out of the equation, and write similar code with > plain mod_perl modules. I was not able to get it so that several mod_perl > processes are involved. In fact, only one mod_perl process got started > this time. That is extremely strange. Are you certain that this behaviour is correct ? AxKit does not modify Apache's idea of when it ought to spawn processes. > How can I workaround this problem so that I can have a running site as soon > as possible ? What's the best way to go in the long run ? The best way is probably not to cache in memory. -- _______________________________________________________________________ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com ----------------------------------------------------------------------- Sex is not the answer. Sex is the question. "Yes" is the answer. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
