On 29 Jun at 21:47 Jonathan Vanasco <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>
> > 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. > [snip] Well, it is my intention that the modules should be reloaded if they've changed; that's the whole point of using Apache::Reload, so I'm pleased it works. Presumably, if they haven't changed, the only performance hit is a stat to the file system, and then only on those modules which explicitly call Apache::Reload. I think I can live with that :) However, without the ability to restart the server, and short of renaming the files, how should I update my software? It won't happen much at the production end, but it will certainly happen. Shouting Never, Never, Never is all very well, and undoubtedly good advice, but it's a bit impractical without an alternative. What are the other problems you refer to? I've been lurking on this list for some months, but have not seen anything mentioned, and Google doesn't throw up anything on the first few pages. Anyway, this all pales into insignificance against the real problems which started this thread; I'd really appreciate some pointers as to how to fix those. Cheers, Tony -- Tony van der Hoff | mailto:[EMAIL PROTECTED] Buckinghamshire, England
