3 ms·
Not this again, we already went through this a few weeks ago. In-fricken-deed... We have been through this problem again and again and again, in different OSe
by joe_the_user 15y ago
Not this again, we already went through this a few weeks ago.
In-fricken-deed...
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.
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". 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.
Consider. 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. It's just data to it. It's not like the computer is intelligent or anything. 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. Hard problem even with the powerful tools that have evolved for solving it over the years. So when a given memory management scheme works, it isn't really "fixed", it just has been tuned for the corner-cases that are shouting loudest on the help lines.
And yes indeed, it is "funny" how just getting the "simple stuff" to work is a hard problem. IE you can find lots of simple examples where the standard solution seems fail terribly.
Angry how your 100 GB memory machine isn't faster? Look under the hood and you'll find Scotty from Star Trek shouting "Captain, I'm allocating your memory as fast as I can Sir..."
- Intermernet 15y ago> the solutions to it that any of these OSes have are tuned-black-magic-split-the-difference-haphazard affairs. I remember reading a book that was basically annotated Linux 2.4 kernel code (Brilliant book, taught me lots, now can't find it) that discussed the, very deliberately, sloppy method of allocating which tables to swap, and when. The justification was that, similar to scheduling process time-slices, the processing penalty of finely controlling every request outweighed the error correction penalty that was inherent in actual testing. AFAIK the 2.6 and 3 series kernels have even more "tuned-black-magic" under the hood. I'd hate to even think what my Windows 7 machine behind the scenes... I've often worried that a windows core dump might actually summon Demons from the Dungeon Dimensions (thanks TP)
- JoeAltmaier 15y agoIf you're not oversubscribed, it shouldn't thrash. Isn't that the complaint? Then its a legitimate issue.