On Jun 29, 2007, at 4:09 PM, Tony van der Hoff wrote:
Well, thank you for that advice.
Um, Why?
How does that help solve my problems?
Apache::Reload checks perl modules and *reloads* them on every hit if
they've changed. It's essentially saying "hi, i'm running under a
persistant environment , where code shouldn't be changing, but I'm
going to take a performance hit each time". you get a perfomance hit
AND you start to lose memory ( stuff goes from shared to unshared )
it also performs very awkwardly and has been the cause of numerous
problems on this list. its likely not the culprit of the problem
you're seeing now, but it will be causing many issues down the road.
its not meant for production, its geared for dev servers.
// Jonathan Vanasco
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| CEO/Founder SyndiClick Networks
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| Founder/CTO/CVO
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
