5 ms·
How bizarre. In the 1993-94 time frame, one of the big talking points about Windows NT was that it was the only OS with an integrated file system cache. That wa
by bediger4000 13y ago
How bizarre. In the 1993-94 time frame, one of the big talking points about Windows NT was that it was the only OS with an integrated file system cache. That wasn't true even at that time, as Solaris also had such a cache, but such is the nature of propaganda.
I'm tickled that what once was a big "technical" advantage becomes a major source of confusion. Presumably, OSes of Windows NT heritage have retained file system caching, which offers a huge performance benefit. Why don't Windows users have confusion over this issue? Doesn't Windows offer an easy way to check or is the whole thing presented clearly, or is Windows so complicated not many people get this far?
I'll also draw a parallel to DUI - without a breath-o-meter, DUI is a lot like driving while distracted. It's impossible to quantify, and therefore not that much of a crime. With a breath-o-meter, or with "top", it's possible to put a number on drunkeness or lack of free memory, and the whole thing becomes a problem.
- chiph 13y agoFrom what I can tell, Windows does not show the disk cache allocation in Task Manager. So even though all the RAM is likely in use, that is hidden from the user. You can probably see it in PerfMon, as that is less "typical user" oriented.
- rplnt 13y agoIt's not in the graph but it's there in the "Cached" field.
- tracker1 13y agoIn windows 7, take "available" and subtract "free", that's your cache usage. Windows Vista started using RAM very aggressively for caching, including pre-filling cache with frequently used pages (apps/data) from disk... ReadyBoost was basically an extension of this...
- Lagged2Death 13y agoWhy don't Windows users have confusion over this issue? Windows' Task Manager has generally counted memory occupied by the disk cache as "available."
- tanzam75 13y ago> Windows' Task Manager has generally counted memory occupied by the disk cache as "available." Windows Vista got lots of complaints about memory usage, because Task Manager listed memory as Total, Cached, and Free. People saw that "Free" was close to 0, and complained that Windows Vista ate all their RAM. Windows 7 changed this to: Total, Cached, Available, and Free. People saw that they had a lot of "Available" memory, so they didn't panic. Well, most of them didn't panic. Windows 8 removed the "Free" line entirely, and now lists memory as: Total, Available, and Cached. If you care about the actual amount of free memory, you can run Resource Monitor or Process Explorer.
- bjourne 13y agoBecause there are a lot of things in linux/unix-land that is completely braindamaged. But they have been with us for so long that they become impossible to change. Like dotfiles, the ps command and Linux memory handling. Windows 8 has a nice graph which shows memory usage over time in which the filesystem cache is not visible. If it was included, memory usage would constantly hover at about 90% which wouldn't be very useful and very confusing. When Windows XP was introduced famous tech journalist John Dvorak complained that "System Idle Process" was using 99% of his cpu and slowing down his computer. In later Windowses, System Idle Process is no more. Also even when you subtract the fs cache and get number of megabytes free memory you have available. That number has almost no bearing on how many number of megabytes an application of yours can allocate. Linux memory management is much more complicated than that.
- ris 13y ago> Linux memory management is much more complicated than that. I don't know if I'm being trolled, but memory management in any modern OS that makes proper use of shared memory is fundamentally very complicated. I suspect what is happening is Windows is lying to you to give you a simple (though essentially wrong) answer.
- mortenlarsen 13y agoIt was at least changed to lie to avoid complaints from users. I remember that running taskmgr.exe from an XP machine on Vista gave a more accurate info, ie. no lying to keep ignorant users happy.
- lmm 13y agoNT was able to use a simpler (maybe not simple, but simpler) design because it was written from scratch once we knew that caches and buffers were desirable. So it's got a unification of swap and cache that would be difficult to retrofit onto *nix.
- AnthonyMouse 13y agoThe Linux kernel and the NT kernel are approximately the same age.
- stonemetal 13y agoWhy don't Windows users have confusion over this issue? Because windows users don't care about how much memory a particular application is using. New Windows developers get confused by it all the time. There are plenty of questions on stack overflow where someone is using task manager to try and measure their application's working set.
- gtirloni 13y agoAn overgeneralized question deserves an overgeneralized answer. Well done.
- stonemetal 13y agoNot sure what you mean. There is a general lack of sophistication among windows users, so they believe what the system is telling them if they go so far as to even ask the question. Among developers it is well known that, that number is at best wrong. If you actually want to know that number use a memory profiler. If I wanted to know about memory consumption on Linux I wouldn't be looking at top I would be looking at valgrind. Top and task man are like stepping on the scale to keep track of your weight the exact number doesn't mean much, and it regularly varies in an unmeaningful way vs a memory profiler which would be like a high precision body fat measurement. Right tool for the job and all that crap.