Re: Memory Issues

[prev] [thread] [next] [Date index for 2005/02/10]

On Thu, 2005-02-10 at 16:56 -0200, Leo wrote:
> As a slight adaptation, I could have an apache server dedicated to each 
> virdual domain waiting on some high port number.  And configure a 
> lightweight apache on port 80 (serving lightweight stuff for all domain) 
> to redirect (using mod_rewrite perhaps) domain specific domain mod_perl 
> calls to those high port numbers?

Yes, although I think you mean "proxy" rather than "redirect."

>  However the configuration of my 
> lightweight apache seems daunting.

It's not very hard to set up reverse proxying.  You don't even need
mod_rewrite for the basic things.

> Use the startup handler (called during startup before the child 
> processes are spawned right?) to calculate what the "application data" 
> should be and intialize the tied "mod counter" hoping that it will never 
> change :(.   I suppose when the machine goes into production, if changes 
> should occur infrequently or upon modification of certain data then you 
> simply restart the server and thus keep this readonly "application" 
> stuff in a shared memory space.

I'm not quite following what "mod counter" is, but loading static data
at startup is pretty common.

> Is there a 
> way update data in shared memory without apache creating a local copy?

No.  To share read/write data, you should use something like
Cache::FastMmap or BerkeleyDB instead.

- Perrin