on 2013-11-21 15:41 LuKreme wrote
On 21 Nov 2013, at 12:26 , steve harley <st...@paper-ape.com> wrote:
Safari claiming 11GB of real memory
That seems excessive.
indeed, but it is just taking what it can; it would probably be lower if the
machine didn't have 16GB RAM, or higher if there weren't other apps competing
for RAM; in other words, in itself real memory is not a full measure of memory
status of an app
and 143GB of VM!
That’s completely irrelevant.
first note that this was VPRVT, not VSIZE
knowing that VM is a matter of mapping address space, some of which is never
used and/or never transferred between RAM and disk, i still have a hard time
imagining what would need to be mapped to reach that figure, and it correlated
strongly with big performance problems
in the above case i didn't capture swap usage, but another time i recorded what
may be a different syndrome — 8GB of real and 19GB of VPRVT for Safari Web
Content (aka WebProcess in top); in this case, with no other "giant" processes,
i had 30GB of swap in use; the implication is that a substantial portion of
VPRVT represented data moved at least once between RAM and disk; in both cases
system response was terrible due to swapping, and quitting and relaunching
Safari with the same tabs brought performance back to normal for at least a
couple of days
_______________________________________________
MacOSX-talk mailing list
MacOSX-talk@omnigroup.com
http://www.omnigroup.com/mailman/listinfo/macosx-talk
