numinasthmatic wrote:
Don't eat crow. It isn't "an application." It's the worst memory management you can get. Go googling on this topic, and you'll find more and more folks realising that OS X memory management is garbage.
https://discussions.apple.com/thread/3221471
https://discussions.apple.com/thread/3533916
https://discussions.apple.com/thread/1858205?answerId=8775428022#8775428022
https://discussions.apple.com/thread/3114607
https://discussions.apple.com/thread/2156286?answerId=10752742022#10752742022
https://discussions.apple.com/thread/1401416?start=15&tstart=0
http://www.osnews.com/comments/25861
http://workstuff.tumblr.com/post/20464780085/something-is-deeply-broken-in-os-x- memory-management
Do your own search. See how many of these you can turn up.
I could probably search more, and find even more people having problems with OS X memory management.
I read most of every link you posted above, either, the problem was solved to be a third party problem, it was an old post that probably has resolved itself (and again probably user error and third party problem), or the problem was actually solved! None of these cases, and the more that I found, were not actual problems with OS X memory management.
Just like in Windows, it's not recommended to modify the memory management processes. I saw many cases of where people were modifying the paging, or VM activity, and any improvements were an eventual, illusion. I thought deactivating the dynamic pager was a pretty crazy idea! I suppose if you don't run out of physical memory, but still, that could cause problems even if you have memory left over. I'm going to try that with a Windows machine and see what happens (I don't think it'll turnout very well).
Memory Management in OS X seems to be very good. I have seen programs that use a lot of memory, my only annoying thing I found is the OS X will only use up to 63 Swap files (just under 64 GB, or 59 GiB; GibiBytes) when I had a program that needed more memory. This (third party) program was horribly bad with memory usage, but OS X did a beautiful job of supplying the memory. OS X actually "paused" the program without it crashing, until it found more memory, when I freed up more memory, it resumed. (Pretty cool! I've only seen this once). I thought that was impressive, pausing a program till it get's more memory. (Again, the program itself a horrible job of using memory, it could have done more with less memory if written better, and it wasn't an Apple program!)
Again, every link you posted, it was a third party process/app, or user error that caused the "problem" (or apparent problem) in OS X memory management.
Right now, I'm using 11.8 GB of RAM, less than 1 GB is inactive, I have 16 GB total. There are 2.11 GB of page ins (ok/good thing) and 0 GB of page outs (very nice thing), and 0 GB of Swap used (obvious, and nice also). (There is of course a 64 MB swap file "swapfile0", it's always there).