thank you for correcting your link.
Windows 7 Optimizations and Default Behavior Summary
As noted above, all of today’s SSDs have considerable work to do when presented with disk writes and disk flushes. Windows 7 tends to perform well on today’s SSDs, in part, because we made many engineering changes to reduce the frequency of writes and flushes. This benefits traditional HDDs as well, but is particularly helpful on today’s SSDs.
Windows 7 will disable disk defragmentation on SSD system drives. Because SSDs perform extremely well on random read operations, defragmenting files isn’t helpful enough to warrant the added disk writing defragmentation produces. The FAQ section below has some additional details.
Be default, Windows 7 will disable Superfetch, ReadyBoost, as well as boot and application launch prefetching on SSDs with good random read, random write and flush performance. These technologies were all designed to improve performance on traditional HDDs, where random read performance could easily be a major bottleneck. See the FAQ section for more details.
Since SSDs tend to perform at their best when the operating system’s partitions are created with the SSD’s alignment needs in mind, all of the partition-creating tools in Windows 7 place newly created partitions with the appropriate alignment.
was it amateur writer day on MSDN? because the reason defragging is disabled for SSDs is NOT that "defragmenting files isn’t helpful enough to warrant the added disk writing defragmentation produces"
Defragging an SSD reduces performance and lifespan at no benefit because the OS has no direct access to data, instead it goes through an abstraction layer to facilitate wear leveling, where virtual addresses are given to the OS which correspond to shifting physical addresses. Defragging the virtual addresses is worse then worthless, it causes harm.
Will Superfetch be disabled on SSDs?
Yes, for most systems with SSDs.
If the system disk is an SSD, and the SSD performs adequately on random reads and doesn’t have glaring performance issues with random writes or flushes, then Superfetch, boot prefetching, application launch prefetching, ReadyBoost and ReadDrive will all be disabled.
Initially, we had configured all of these features to be off on all SSDs, but we encountered sizable performance regressions on some systems. In root causing those regressions, we found that some first generation SSDs had severe enough random write and flush problems that ultimately lead to disk reads being blocked for long periods of time. With Superfetch and other prefetching re-enabled, performance on key scenarios was markedly improved.
So, super-fetch caused "marked improvement" in tests with an when ENABLED. However, the article claims it will be disabled on HIGH performance SSDs because their performance is "adequate" enough to not need it.
this does not say that it degrades performance on those drives, or that it doesn't improve it, only that it isn't "needed"... furthermore, this is also false because in reality, superfetch is enabled on high performance drives. So whomever said that was wrong about that claim.
plus, you know:
An SSD boasts access times about 100 times faster then a spindle drive, and throughput about 2 to 2.5x.
Ram boasts access times MILLIONS of times faster than a spindle drive, and a throughput ~100x greater.
I leave it up to you to deduce how much faster ram is than an SSD.
I am shocked we are still in disagreement about this specific issue, but whatever, we have both presented our opinion, a plethora of information, and line by line quotes.
So I think its enough about that particular issue, anyone reading this argument can see for themselves who they think is right about this issue (hint: its me... or is that my admittedly massive self esteem again?
)
jokes aside... is there another particular issue you take issue with?
Facebook
Twitter