New
#11
I can only speak from experience. The everyday Vista user is frustrated at why their PC requires 5 - 10 minutes before their PC is responsive to what they need to do. Even Microsoft engineers suggest users wait until Vista completes its caching (from Microsoft springboard series).Caching helps prolong the use of SSD drives, the life of a SSD drive decreases with each read/write
I will say that from reading your current posts that you dont have a reasonable idea how the memory caching works at all, If you took the time to learn about the changes and research/run tests then you wouldn't have any problem with it....I just started an extra 30 instances of Visual Studio just to show some examples here...
Attachment 22552
Look at the collums for each process, each instance of Visual Studio (devenv) has commited 21mb of data, has an available working set of 27MB available, currently shares 19MB between each process with an actual real memory use of 7MB (private).
You will notice all the instances of Visual Studio are sharing 19MB with a Private memory use of 7MB, after the first instance is running Windows is able to use that existing process's shareable memory for launching each new process and share xxx amount of ram with that process resulting in an actual private use of 7mb saving 20MB for each new instance I create, A classic example of these improvements with Memory Management if Firefox, You will notice its first launch after booting up your system is really slow but each new instance after that is launched near instantly.
That just never happened on XP, all these instances of Visual Studio would have consumed 27Mb of ram each instead of 7MB and ate all my available RAM.
You also have idea that the cached ram is actually slowing your applications down, You can see from the screenshot that I have 30mb of free ram with 2.1GB of cached ram... For example, when launching TF2 or CSS they query the amount of available RAM and reserve about 400mb each, Windows simply doesn't inform the requesting application that its using that ram for caching and consequently CSS/TF2 just over-writes the memory addresses its using, theres no unloading/clearing/deleting or whatever your thinking is going on that could possibly slow your system down... If it has to write data onto your page-file or something then it will defintly cause a slow down while that takes place.
BTW, Look at the Hard Faults/Sec graph on the right, That is your actual read/write usage of your RAM and you can see its almost nothing even though Im using 2gb RAM right now, That was also non-existent on XP and it would be constantly read/writing to your RAM resulting in a massive slowdown when your maximum RAM capacity was reached.
You could be listening to music, playing games, burning a DVD and transcoding a Movie and whatever else without even realising you had zero ram available provided you had a minimum 2-4gb ram installed, Yes you would notice a slow down while switching between applications but launching instances of current applications is near instantaneous and thats also something you could never do on XP.
Microsoft devs know more about Windows and its core management than anyone else, their much smarter then you or me and dont just do things because they feel like it, they play games, watch movies, burn dvds...etc just like "normal people" and dont just go around changing things because their bored, just like us...they want better management of things like Memory usage but hey if you feel that your smarter then you more than welcome to go ahead disable what you feel like.
Windows Vista Performance Roundtable
http://technet.microsoft.com/en-us/w.../aa904820.aspx
Technical Chat with Mark Russinovich
I think we can all agree that Vista was/is the beginning of the end for Microsoft. This crazy obsession of launching applications instantly when 99% of applications launch pretty much instantly off HDD/SDD anyway is just one example.
And Ubuntu plus other Linux distro's aren't exactly performance wizards even on high spec hardware!
Ultimately the biggest looser in this massive gamble with re-engineering the memory management of Vista / Windows 7 is foreground application and Explorer shell responsiveness. And Microsoft still haven't listened with Windows 7.
Lets hope Google understands what users need rather than giving users a slow bloated OS that even Intel wouldn't touch alongside every large enterprise I have worked for. 2010 will be an interesting year as many IT teams begin to deploy Windows 7 to small test groups of Windows XP users.
Quote