Hard problem even with the powerful tools that have evolved for solving it over the years. Why do you think they call it "random-access-memory"? The problem of dividing up chunks of memory for application programs to use is as hard as dividing up that hard disk for large and small files to live in, EXCEPT that application programs expect to be handed a chunk of contiguous memory when they call malloc. It's not like the computer is intelligent or anything. Either the machine keeps all your information in memory it or keeps on-disk and in-memory and either way, the machine hasn't a clue what information is important to you, my friend.
Winamp for mac mountain lion full#
Which is to say "you might not like senseless disk-thrashing but would you rather have your machine randomly freeze when it got out of memory?" And scratching a little more, it comes down to admitting that memory-allocation is a hard problem in its full generality and they don't teach you that in application-programmer-school, and further that the solutions to it that any of these OSes have are tuned-black-magic-split-the-difference-haphazard affairs.Ĭonsider.
It usually ends with a "neck-beard" saying with enough authority "look, really, they are doing it right even if it seems totally illogical to you and any brokenness is just your configuration, little man". We have been through this problem again and again and again, in different OSes, at different times and with different things triggering the various problems. Not this again, we already went through this a few weeks ago. Its a hard problem, and both OSX/Windows choose the best possible solution you can heuristically. The only time its "wrong" is when I start using those processes again, which takes all of 1-2 seconds. Why SHOULDN'T that memory be reclaimed and at the ready for a new program or some other request? Its just going to page it out then and likely take longer to do.
Most of the swapped files belong to things like my ruby+pry repl, a clojure repl I haven't touched for 2 days, and other random things I don't use often enough to warrant they stay in active ram. My iMac at home has 16g of memory and 400g of swap used right now (8g active, lots of file cache that'll get purged). This fetish people have with their OS using swap at times seems to border on the ridiculous side.
Winamp for mac mountain lion free#
Swap use when there is free memory isn't a bad thing. Second guessing it all the time just makes its job harder. Which is what the VM subsystem is there for. The "speedup" is not a speedup for your use, its to allow for better memory management. So swapping out their memory that hasn't been used for N hours isn't a bad thing.Īnd yes, the logic is sound, its better to use a bit of swap for an infrequent daemon and let 4-5 megs of memory be at the ready if needed than leave it in place all the time. They don't need to be in ram all the time needlessly. The logic is for things like daemons or infrequently used processes that wake up maybe once a day.
0 kommentar(er)
