What's The Deal With Write-Cache Buffer Flushing?
Intel recommends against disabling write-cache buffer flushing on its SSDs. And based on our benchmark results, we see why.
In order to generate a more visual understanding of this feature's impact, we singled out the effects of disabling write-cache buffer flushing on Intel's X25-M using the CrystalDiskMark 3.0 x64 write test. The following results represent performance after a SE, with all of the tweaks performed, and with all of the tweaks performed, plus write-cache buffer flushing enabled.
When each of the tweaks is applied, including disabling write-cache buffer flushing, Intel's X25-M takes a major performance hit in all of the relevant metrics (especially the 4 KB random writes, which drop down to the 4 MB/s range).
When write-cache buffer flushing is re-enabled, performance jumps back up to the same level seen from the freshly Secure Erased drive. This is definitely a modification to avoid on a drive that employ's Intel's proprietary architecture.
Hibernation: Amount of space saved by turning this off is equivalent to the amount of RAM in your system. Not limited to 2GB.
Also, hibernation has benefits over standby where hibernation will allow your system to return to a fully working state after removing power whereas standby requires power to still be supplied to your system. Laptops for example you'll want to hibernate to avoid discharging the battery while in sleep mode.
Thanks for another excellent article -- I'm surprised I haven't seen an article on this subject that's as comprehensive. Toms to the rescue.
Thanks for pointing both of these things out. You're absolutely correct about indexing.
I've updated the story for the author to reflect hibernation as well. I added clarification re: desktops and notebooks, though I'd suggest powering down a notebook with an SSD is comparable to putting it into hibernation. I don't think anyone would recommend putting it into standby; as you mention, that continues to drain power.
All the best!
SSD's are changing faster than any other computer technology. The current generation SSD's are already twice as fast as the SSD's tested in this article. Tom's Hardware is being left behind in the dust with reviews like this.
disabling system rstore is usually a good idea, sometimes it's better to just limit it's size form the 10% default value.
swap disabling is not a good idea, as you said. i'd rather have the swap on a secondary, mechanical drive.
indexing is very useful. you can relocate the address to where indexing data is stored. i put it on a mechanical drive.
disabling superfetch and turbo cache are really useful. ssd may be faster than hdd, but they are weak compared to ram speed. read caching really makes a difference.
hibernation file is not really useful on a desktop but it's a matter of taste. better have it on a mechanical drive if possible
another thing that really helps is putting firefox profiles on a ram drive. i develop on visual studio and there is a directory where lots of small files are written on build. having this temp folder on a ramdrive helps a lot regarding speed and writes as well.
1. save power
2. restore the previous work withou having to start everything
I use hibernation a lot on my desktop just because I can leave all the network independent applications running and just power down. after power up, I am in the previous environment state and can immediately continue whatever I was doing before. No need to start applications and reopen saved files.