^ Utterly fails to address one single issue I raised.
Yes, my "computer runs faster when it caches data in RAM instead of on disk," but I'm talking about when that Inactive Memory "cache" starts paging to disk. Seems to me that there's no excuse for Inactive Memory ever hitting the hard disk virtual memory scratch files; it should just be "forgotten" at that point. "High inactive RAM" may be what I want, but it is precisely when Inactive Memory becomes high that the disk thrashing & sluggishness begins. If running the script (or Purge, which is what I do when it happens) "makes your computer run slower," then why does doing so restore my robust performance to that of a freshly booted computer? Indeed, before I discovered Purge, I had to wait for a reboot to clear things up, when that wait became preferable to a miserable ongoing fit of usability-sucking spinning beachballs and accumulating scratch files.... And to repeat, no matter how much RAM one adds, it only delays the performance hit until Inactive Memory eventually fills up. (If you watch Inactive Memory, it often rises & falls with use, but sooner or later something you're doing will not occasion its reclamation, and when it "red-lines," that's when the usability degradation commences.)