Poor displayresource Debt Management in Linux
 |
I booted into Mandrake 10.1 a little while ago, loaded up a Nautilus window, Kaffeine (with no video launched), and Gnome System Monitor. Started moving the Kaffeine window around on the screen, and watched the CPU usage indicator go over 90%, just moving that one window with no video playing?!? Huh?!?!?!
I figured that can't be right, so I closed Gnome System Monitor and launched KDE System Guard and did the same thing - moved a single Kaffeine app window around on the screen with my mouse. Again, the CPU usage goes skyhigh, into the mid-to-high 90% area?!
I noticed something from your other post about Linux being slow: The Intel video chipset has had...
At this point, I don't get it. Just this past Thursday cola moron Bagger Vance was laughing at Windows, saying "LOL! Move an app, and use up the CPU." and "When will windopes ever learn how the computer works?!" Now I'm seeing that just moving one window around consumes 90% of the CPU? How?
So I boot back into Windows, launch equivalent programs (Windows Explorer, Windows Media Player (no video launched), and Task Manager. Started moving the WMP window around, and the CPU usage never went above 20%!
(the spikes - none higher than 40% - are where the apps were first opened).
Notice there are 80 processes launched in Linux consuming 284mb of memory, but 52 processes started in Windows consuming 421mb of memory. That's because I loaded a bunch of bigger programs (Oracle, SQL Server, 2 Apache monitors, Firefox, MS Access, etc) in Windows - to try and "cripple" it before the test.
I explored the Linux processes in KDE System Guard. Odd. Linux starts a boatload of tiny processes that do one little function; I didn't write them all down, but I'm talking about things like kwrited and kwin and mingetty. (by the way, KDE System Guard absolutely blows away Task Manager for sheer information presentation, functionality and usability).
System is P4, 2.0ghz processor, 1gig PC2700 DDR memory.
Anyway, what gives? Am I just confused, or does Windows GDI processing efficiently and totally and completely decimate the CPU-hogging Linux X Windows system?
Say it ain't so!