dreammjpr wrote:
I explained in the same post that you can tell the difference between properly used RAM (wired) and the RAM used up by the file cache by subtracting 'wired' from 'used'
Say you have 6GB used RAM and the wired memory reports only 2.8 GB (usually the case when none of your applications are running). 6 - 2.8 = 3.2 Gb
3.2 Gigs are being used by the cache, but since we're not running anything beyond the daemons and finder, we have about 2.2 Gb wasted by the cache and you can summarily execute it with purge.
Next time you run a program it will be loaded into memory as normal and you will only have the minimum necesarry caching of program routines into the file cache
Users are always supposed to be aware of their memory resources, how much a large program typically needs and in what conditions to best load it.
I personally have no problem with the theory of file caching, as long as the OS releases it immediately when something else wants the memory. I found that on my particular machine (mid-2009 13" MBP, which I believe is not working with Mavericks as Apple intends), with memory compression operating, the file cache would grow quite large and the system would prefer to compress memory before releasing file cache, which, again, for my machine, was incredibly slow. Once I turned off memory compression, file cache released normally and everything is fast as expected. I don't have to worry about purge. You might try turning off memory compression to see what happens. http://superuser.com/questions/668114/disable-compressed-memory-in-mac-os-10-9-m avericks