* Herman Knief (herman@knief.net) [011101 19:35]: ->Why the hell is everyone so concerned about the use of some swap space? Because as stated before "This is a bug!" ->Is the computer thrashing the disk? Yes! ->Has performance dropped to an unbearable level? Yes, a large chunk of memory is suddenly dumped to swap and the system slows to a crawl. ->Just because the system reports that some swap has been used or allocated, ->does not mean that the swap space is active. Not "some" 30-140+ megs gets shoved to swap for NO REASON that us non-programmers can figure out. ->Have you looked at vmstat? No, I watch system usage via Gkrellm. ->Like many things on Linux, once a resource is allocated, it is not free'd... ->it just remains allocated. If the the system was thrashing the disk, then ->I would say there was some cause for concern. Well, this is true to a point, but if you have 100+ megs of FREE ram then it shouldn't take that and leave swap alone until it's needed. And once RAM is freed then swap can be flushed and it does flush..I've watched it do so. ->Quite frankly, with the VM that was used from 2.4.0 to 2.4.9, ->I was alsways a bit concerned about the apparent lack of swap use, as ->once the real memory was consumed the system would become unuseable as ->it thrashed to try and find resources. Well, you shouldn't be concerned. This is how Solaris and many other Unix OS's work. Only Wintendo will use memory in this fashion and it's a bad design. Unix uses ram first then swap because it's always faster to execute operations in RAM then on the harddrive. As I have said to many, many people over the years on this list.. You should take Yoda's advice and "Unlearn what you have learned" because it's just plain wrong and I hope Unix/Linux never, ever starts to do this. But we know from the release notes that the problem surfaced in .10 and was fixed in .14pre6. There were several releases over the past month so it's not like the issue existed for years and is now being changed. It was recognized as a bug and has been fixed. We are just waiting for SuSE to test a kernel with the fix and release it which should thankfully be soon I hope to God... And I have never had a Linux/Unix system thrash because it ran out of memory and couldn't find it's swap if it needed it. Unix and Linux are much better at recovering memory from programs that have been closed then any Microsoft OS has ever been. Also, a side note...I'm not going off on MS just to do it...and don't explain how Microsoft OS's work. Before I started working with Unix I use to be a quite skilled NT Admin..so I know what I'm talking about. ->The OOM Killer is a great concept.. unfortunately, it doesn't work. ->I personally, much prefer the model of 2.2.x, unfortunately I need ->some of the features of 2.4 Well, can you point out when the 2.2.X kernel opted for swap over physical memory? The first kernel I used was 1.1.13 and just about every 2.2 kernel up to 2.2.18 when I switched to the 2.4 kernel with the .2 release. I've never see this behavior... -> so I welcome the VM rework that has been done in 2.4.20, and from the ->testing I've done on heavily used NFS servers, it is much more stable... ->even if it does claim some swap has been used with free memory left. 2.4.20 doesn't exist :) ..they are working on 2.4.14 hence the pre6 just being released. I'm a systems admin for 4 large Solaris clusters that use NFS quite a bit to run some 600,000 domains and they do not behave like you discribe..if they did I would look for a patch on Sun Solve. :) ->Of course this is just my opinion... True..and hopefully we can educate you on the Unix/Linux way :) Cheers! And remember have fun! -----=====-----=====-----=====-----=====----- Ben Rosenberg mailto:ben@whack.org -----=====-----=====-----=====-----=====----- "Technological progress is like an axe in the hands of a pathological criminal" -AE