<div dir="ltr"><br><br><div class="gmail_quote">On Fri, Dec 16, 2011 at 11:43 AM, Shlomi Fish <span dir="ltr"><<a href="mailto:shlomif@shlomifish.org">shlomif@shlomifish.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all.<br>
<br>
I reported a bug in Amarok ( <a href="https://bugs.kde.org/show_bug.cgi?id=288876" target="_blank">https://bugs.kde.org/show_bug.cgi?id=288876</a> )<br>
where it sometimes consumes over 10% of my RAM on startup, and it was closed<br>
with this comment:<br>
<br>
<<<<<br>
Well, there is the virtual memory but it is the residual memory use that<br>
matters. Yours us just 371M which is absolutely correct.<br>
FWIW: I suggest you read up some documentation on dynamic memory use in Linux.<br>
In short: the more memory available, the more will be used, the system<br>
distributes this evenly to the running processes depending on their priority.<br>
<br>
Not a bug.<br>
>>>><br>
<br>
Well, I don't understand it. What is "residual memory" in this context (as<br>
Google searches for it yields junk.), and why is still OK that Amarok consumes<br>
so much.<br>
<br>
Any insights would be appreciated.<br>
<br>
Regards,<br>
<br>
Shlomi Fish<br>
<br>
<br></blockquote><div><br>I would assume he meant RSS[1], as opposed to VSZ ('VIRT' in 'top'). A program can ask for a huge amount of memory but not use it, so it won't actually waste your resources...<br>
<br>[1] <a href="http://en.wikipedia.org/wiki/Resident_set_size">http://en.wikipedia.org/wiki/Resident_set_size</a><br></div></div><br>-- Shimi<br></div>