VirtualLarry
No Lifer
See this thread (since someone did not move it to OS)
-
We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.
Vista's disk cache is bugged?
- Thread starter VirtualLarry
- Start date
The linked blog post completely gets rid of the context, making it sound like something completely different than what it's really about.
Click through to the link to get the whole story:
http://blogs.msdn.com/ntdebugg...e.aspx#ntdebugsurvey24
The first thing to be very clear about: This isnt a vista issue.
Again...this has *nothing* to do with vista specifically. The blog post from the OP just pulled vista out of his ass and threw it in there, and clearly doesnt understand anything he posted - he just needed an excuse to bash on vista ( a common thing). This is actually one of the things that vista actually tries to prevent through superfetch, its been a problem for any OS as long as I can remember.
The basic idea is that excessive reads or writes can grow the cache to the point where it starts to push into the memory used by programs. This is due to either ill-behaved programs, or programs that need to torch I/O to the point where the entire system is more concerned with it than anything else.
The one app that comes to mind that seems to cause this kind of behavior are the bitorrent downloaders - if you're downloading a 4gb iso for instance, and reads and writes are taking place throughout this entire file, it kinda starts to take over your entire system as it can't really keep up with it unless a lot of cache is devoted to it.
Other than that, it's really not something that props up in day to day usage. It's much ado about nothing by someone who doesnt understand what theyre reading.
So essentially, too much cache is a bad thing when it comes at expense of your running programs. This is not what vista or superfetch does - SF only fills "empty" memory.
Click through to the link to get the whole story:
http://blogs.msdn.com/ntdebugg...e.aspx#ntdebugsurvey24
The first thing to be very clear about: This isnt a vista issue.
Again...this has *nothing* to do with vista specifically. The blog post from the OP just pulled vista out of his ass and threw it in there, and clearly doesnt understand anything he posted - he just needed an excuse to bash on vista ( a common thing). This is actually one of the things that vista actually tries to prevent through superfetch, its been a problem for any OS as long as I can remember.
The basic idea is that excessive reads or writes can grow the cache to the point where it starts to push into the memory used by programs. This is due to either ill-behaved programs, or programs that need to torch I/O to the point where the entire system is more concerned with it than anything else.
The one app that comes to mind that seems to cause this kind of behavior are the bitorrent downloaders - if you're downloading a 4gb iso for instance, and reads and writes are taking place throughout this entire file, it kinda starts to take over your entire system as it can't really keep up with it unless a lot of cache is devoted to it.
Other than that, it's really not something that props up in day to day usage. It's much ado about nothing by someone who doesnt understand what theyre reading.
So essentially, too much cache is a bad thing when it comes at expense of your running programs. This is not what vista or superfetch does - SF only fills "empty" memory.
VirtualLarry
No Lifer
I know in Windows 9x, there was a very valuable system tweak to limit VCACHE from taking too much memory away from programs.
soonerproud
Golden Member
Windows has not been based on the 9x code for over seven years so I really don't see what relevance this has on the subject. Looks to me like you are just grasping at straws now that your original post has been debunked.
Cache is rarely going to eat into program memory in the first place. It would be a solution for a problem that doesnt really exist except under extreme and rare circumstances.
You're going to have to have some faith in the engineers that built this system that know far more about these things than you, me or anyone else for that matter.
From the article it would imply there are some bad edge case scenarios specifically when on 64bit systems with poorly behaving applications. Certainly possible, you'll see the source is from Windows troubleshooting team. These guys are tasked with exactly this, finding those edge cases and fixing them.
If your implying that for most users on a day to day basis this is a problem, well, you just trying to stir the post. If your saying that this could be an issue and should be addressed, sure, looks to me exactly what the developers at MS are doing (e.g. their job)
VirtualLarry
No Lifer
Uhm, it wasn't my post. I was just bringing it to your attention.
I was just pointing out that this isn't the first time that Windows' OSes have had this (or similar) issues.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
