On Tue, 12 Mar 2002, Graham TerMarsch wrote: [...] > We saw something similar here, running on Linux servers. Turned out to be > that if the server swapped hard enough to swap an HTTPd out, then you > basically lost all the shared memory that you had. I can't explain all of > the technical details and the kernel-ness of it all, but from watching our > own servers here this is what we saw on some machines that experienced > quite a high load. > > Our quick solution was first to reduce some the number of Mod_perls that > we had running, using the proxy-front-end/modperl-back-end technique,
You should always do that. :-) > and then supplemented that by adding another Gig of RAM to the > machine. > > And yes, once you've "lost" the shared memory, there isn't a way to get it > back as "shared" again. And yes, I've also seen that when this happens > that it could full well take the whole server right down the toilet with > it (as then your ~800MB of shared memory becomes ~800MB of _physical_ > memory needed, and that could throw the box into swap city). I forwarded this mail to one of the CitySearch sysadmins who had told about seeing this. He is seeing the same thing (using kernel 2.4.17), except that if he disables swap then the processes will get back to reporting more shared memory. So maybe it's really just GTop or the kernel reporting swapped stuff in an odd way. No, I can't explain the nitty gritty either. :-) Someone should write up a summary of this thread and ask in a technical linux place, or maybe ask Dean Gaudet. - ask -- ask bjoern hansen, http://ask.netcetera.dk/ !try; do();
