Re^2: issues with module versions

This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.

Thanx for answer, we use this way too ;0) But it consumes more memory - apache childs, db connections etc...

Comment on Re^2: issues with module versions

Replies are listed 'Best First'.
Re^3: issues with module versions by mpeters (Chaplain) on Oct 06, 2005 at 11:20 UTC
You're right it will consume more memory, but most of this memory is shared (well, in nix land it is, even in some OSes have problems reporting shared memory). You can reduce the number of apache children (and db connections) you need per application by running a simple lightweight proxy in front. -- More people are killed every year by pigs than by sharks, which shows you how good we are at evaluating risk.* -- Bruce Schneier	[reply]
Re^4: issues with module versions by pajout (Curate) on Oct 06, 2005 at 11:57 UTC
Yes, I know... httpd scaling has some limitations, especially, when non-shared part of httpd-children takes ~15M (which is not good state, I know). Imagine, that two similar legacy applications run under Apache, using the same db and sharing some perl modules. But, acidentally, one of them uses old version of MyFamily::Session and the second uses newer version of this package...	[reply]

• hippo

• erzuuli

‥ Anonymous Monks are no longer allowed to use Super Search, due to an excessive use of this resource by robots.


No such thing as a small change
	PerlMonks