Originally posted by siride
View Post
Announcement
Collapse
No announcement yet.
KDE SC 4.7 Release Candidate Hits The Web
Collapse
X
-
Originally posted by RealNC View PostActually, no. free is pretty dumb compared to system monitor. Quite often, free can't be trusted as much as sysmon.
Comment
-
Originally posted by RealNC View PostIt has better (more accurate) detection about free memory, buffers, etc.
Comment
-
The test case I suggested works best in this scenario. I'd even dare to say it's the only correct way of measuring KDE RAM requirements.
If you want to argue with me, then forward my method to Andrew Morton or Linus Torvalds and hear out what they say.
Comment
-
So the KDE RAM usage makes the PC slower or faster?
There is no point in arguing without considering that!
Why nobody is measuring speed? Oh, I see, because performance/responsiveness is more difficult to measure than looking at a single number and yelling "there, RAM wasted!"
But, is it better to have RAM storing pixmaps, app data, or whatever KDE stores, or is it better to leave that RAM for disk cache, and let the system manage it?
I think that, given the choice, it'll be almost always better to let the app decide what's better to store. After all, the app knows best what's most urgent to the user.
Comment
-
Originally posted by DeiF View PostSo the KDE RAM usage makes the PC slower or faster?
There is no point in arguing without considering that!
Why nobody is measuring speed? Oh, I see, because performance/responsiveness is more difficult to measure than looking at a single number and yelling "there, RAM wasted!"
But, is it better to have RAM storing pixmaps, app data, or whatever KDE stores, or is it better to leave that RAM for disk cache, and let the system manage it?
I think that, given the choice, it'll be almost always better to let the app decide what's better to store. After all, the app knows best what's most urgent to the user.
I have 8GB of RAM and almost all the time 2GB or more aren't used. I would be happy if KDE starts using more RAM to become more responsive.
Comment
-
-
Originally posted by birdie View PostThe test case I suggested works best in this scenario. I'd even dare to say it's the only correct way of measuring KDE RAM requirements.
If you want to argue with me, then forward my method to Andrew Morton or Linus Torvalds and hear out what they say.
The alternative is to go through each process and get the total memory used, then try to figure out what's shared and then try to subtract out buffers and caches (which you get from meminfo anyway) and you will end up with something less accurate that takes longer. I'm not sure why that would be a better way because figuring out memory sharing is a real pain in the ass. It's necessary if you want to find out per-process memory usage, but free doesn't even try to do that anyway, so it's moot for this discussion.
Comment
Comment