misc.word.corp wrote:
Yes, this is something that continues to puzzle me -- I'll often run Netscape and Gimp on KDE, and the system will eat up 63 MB's of my memory, but when I launch yet another app, it won't write to swap. Even though memory is getting dangerously low!
Also, as we know, KDE takes up a lot of resources, a large portion of which aren't freed when leaving X and returning to the console. Linux somehow manages to flush out (free up) the memory, however, when returning to X. Again, the swap partition isn't written to.
Any gurus care to speak out about how these memory issues are managed? It's truly one of the unique features of the Linux OS, and I'd like to know more.
A 'guru' I am not, but I think that It could be explained by the enormous buffer when only running x. perhaps by keeping a buffer of 32+ megs, it can access memory quicker and increase performance. it would explain why opening gimp after netscapeonly takes about 3 megs o' swap, but when i close gimp, it frees up 16megs of physical memory, which slowly drains down. -- Aaron Seelye <A HREF="http://revolution.3-cities.com/~roberto"><A HREF="http://revolution.3-cities.com/~roberto</A">http://revolution.3-cities.com/~roberto</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e