| |||||||||||||
Time to thrash the 2.6 VM?Time to thrash the 2.6 VM?Posted Mar 4, 2004 20:45 UTC (Thu) by jwb (guest, #15467)In reply to: Time to thrash the 2.6 VM? by crimsun Parent article: Time to thrash the 2.6 VM? I suppose it would be better to blame the process, but RvR's style of magically tweaking constants strikes me as unscientific. I'd be happier with an OSDL project which analyzed any proposed VM changes (or any kernel change) on a variety of workloads: kernel compiles on 128MB machines, interactive loads on 256MB machines, DVD burns on 1GB machines, web serving on 1 and 2GB machines, database loads on 1, 2, 4, 8, 16, and 32GB machines, and so forth. My enthusiasm for AA's changes stems from his proven history of having insight into how the kernel is really behaving, and his willingness to acknowledge the current brokenness.. RvR's 2.4 VM through 2.4.9 was a disaster. 2.4.10 was the climax, after which the kernel's behavior was so very much more reasonable. And I never forget that RvR invented the OOM killer, probably the worst decision for Linux operability ever made.
(Log in to post comments)
Time to thrash the 2.6 VM? Posted Mar 5, 2004 13:26 UTC (Fri) by Johbe (guest, #249) [Link] I'm having this problem right now. We run a squidproxy for about 1500 clients, a smp machine with approx 4 gigs of ram. Someone suggested I tried out Rik's rmap patch and that's what I'm doing right now.The problem I'm experiencing occationally is a complete lockup, kswapd eating *all* cpu on the machine, it becomes unusable, locked down to ssh and everything for 10-15 minutes then it starts running again as usual. I've been using the rmap patch for 3 days now, and so far, we haven't experienced this problem - it might show up, takes a while after a reboot until it hits. We'll see. But I still have some faith in it.
|
|||||||||||||