On Jun 29, 2006, at 2:27 PM, John Siracusa wrote: > Well, you can't have it both ways. Either you want memory to be > shared, in which case all the class setup and initialization can only > happen once, in the Apache parent process, before the first fork, or > you want everything to update "in real time" with db schema changes, > in which case each apache child will now have its own "dirty" memory > as a result of those updates.
i'm fine with either- i just want to minimize memory use. i'm kind of pushing the limits on the boxes i have already and can't afford to upgrade (they're maxxed out on ram already) > The simplest solution is to restart the server after any db schema > change. yeah, that works. i don't care that this happens, i only change schema in dev. the schema change just alerted me towards the caching issue -- which made me worry about shared memory. > shared memory issue, which is basically intractable. You either do it > in the parent before fork or it's not shared. No (reasonable*) way > around it. parent pre-fork is fine. just trying to minimize production memory. | - - - - - - - - - - - - - - - - - - - - | RoadSound.com / Indie-Rock.net | Collaborative Online Management And Syndication Tools | - - - - - - - - - - - - - - - - - - - - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
