On Thu, Feb 26, 2009 at 12:38 PM, Carl Johnstone <modp...@fadetoblack.me.uk> wrote: > 1) We want to run different versions of the same app for different sites - > this means I have a namespace problem for MyApp v1 vs MyApp v2 etc.
This has been discussed many times on the list. You can't run two modules with the same name in the same perl interpreter, so you either need to change the namespaces for different versions or run separate servers. > 2) The load times for each app are reasonable, however the load time for the > whole lot is now getting towards a couple of minutes. However whilst apache > is waiting for the perl code to load it accepts connections. Two minutes? That's a very long load time. I've seen huge codebases load in 10-20 seconds. I think something might be wrong there, like a slow database connection or DNS lookup. Is the real problem that apache is accepting connections during startup? You could solve that by making your front-end smarter. Some systems, like perlbal, will wait until apache responds to a HEAD request before considering a server up. You could also rig your frontend so that you can manually tell it when a server is on or off using an external script, and use that to take restarting servers out of rotation until you verify they're up. - Perrin
