3 ms·

I remember the Windows SuperFetch* memory caching service getting the same (misplaced, in many cases) complaints for a while after it was introduced on Windows

• justsomehnguy 5y ago
  I'm regularly explain what MS SQL doesn't eats up all available memory like Cookie Monster eats cookies. The most recent instance was just a month ago. Though I like when I ask people to explain why their app/service should /not/ use free and abundant memory to serve their users. That short-circuits their brain.
  • gruez 5y ago
    >Though I like when I ask people to explain why their app/service should /not/ use free and abundant memory to serve their users. That short-circuits their brain. here's a reason: because if chrome decides to eat 1GB of memory per tab, and I only have 8GB of ram, then I can't run anything else if I have more than a few tabs open. If chrome could have gotten by with 0.2GB per tab, then it using "abundant memory to serve their users" doesn't actually serve their users, it makes their experience worse. I suppose the system could work if there was some mechanism for the OS to demand that a program free up memory, but I haven't seen that in practice.
    • justsomehnguy 5y ago
      Obviously the usual context of the discussion was server workloads, often a single role servers, like a before mentioned MS SQL. > I suppose the system could work if there was some mechanism for the OS to demand that a program free up memory, but I haven't seen that in practice. Memory mapped files works exactly like that, IIRC.