Originally published at: http://www.howtogeek.com/165472/6-things-you-shouldnt-do-with-solid-state-drives/
Solid-state drives are different from the mechanical, magnetic hard drives in wide use. Many of the things you’ve done with typical mechanical hard drives shouldn’t be done with newer solid-state drives.
Great list of things not to do. Even for someone like myself in IT, I tend to forget that I should, if capable, alter where programs write their log files etc. It's just something you tend to overlook on any given day.
God one . The best part of the site is that even a noob can understand the language in which the article is written
The first laptop I bought with SSD was the Vaio VGN TT190 running Vista. I still use it occasionally, when I need 2 laptops running side by side. The SSD is quite full and, despite those 2 "don't do" everything is still running smoohly although yes, it is now quite sloooow (at least compared to the new Vaio).
Regarding wiping SSDs, what's the best alternative to DBAN? We're required by our corporate office to wipe old hard drives before retiring computers, doing at least a 3-pass wipe to remove all data and the OS. If you can't use DBAN to do that, what should you use?
How about the "page file". Should we leave this on in a SSD?
What are some examples of programs that heavily write temporary files?
so generally you should not use it. why? because most of the topics you show will make it useless. you generally buy SSD because of its speed. which depends on frequent read and write of your application
I was under the (mis?)impression that Windows 7 defragged drives in the background. Is this false? If not, is Windows 7 smart enough not to defragment SSDs? If not, can the background defragging be turned off?
@mathewsdaniel3 I've seen it enabled on SSDs more often than not. Go to the Start menu and click on “All Programs”, “Accessories”, “System Tools” and “Disk Defragmenter”. Go to “Turn off schedule” and make sure that Windows does not defragment your SSD drive
I think it depends on how Windows was installed. If you do a vanilla install, straight from the disk, Win7 has it enabled by default. However, OEM manufacturers usually (not always) turn it off.
I bought a Lenovo Yoga with a 128GB SSD, and check defrag was the first thing I did when I turned it on. Thankfully, it was already off.
I think you've clearly hit a vein here, HTG, and a lot of completely understandable ignorance and misconception is going to surface as a result. Maybe another article could expand on the "six things" idea and explain why (and how) avoiding the six things doesn't devalue SSDs for either geeks or average users. You left one goodie out, though: Indexing should definitely be disabled on the SSD, because it involves a great deal of reading and writing with absolutely no benefit. The SSD already accesses all files as rapidly as it can. Having an index to refer to might even actually slow down SSD searches, rather than speed them up.
If you install windows 7 directly onto an SSD drive, windows will see that and disable disk defrag for you. If you copy an existing installation over from a mechanical drive to an SSD you have to make sure to turn it off yourself because it uses the settings that were set at the time of the installation until the user changes them
Agree strongly, Indexing on an SSD is not needed on a disk that seek time is non-existent because we don't have to wait for platters to spin up and get to the desired location after finding the file within the mft. You can still have indexing, if you still use windows indexing service, for other mechanical storage drives you may have installed.
Indexing is not because of slower seek time. It is for "Finding" files quick. If I search for a file which contains "my project name", without indexing, every file in the disk needs to be searched. If it is indexed, it can be found from the index in a matter of seconds.
Indexing doesn't require too much writing. And a lot of reading of SSD is not a problem. Only writing can wear out SSD.
So why change to an SS?. Seems not worth the bother after all. The beauty of a computer is its retrieval system. If this ease and convenience is lost with all the caveats of an SSD, then the computer's retrieval system becomes less functional. And while on the topic of retrieval--Windows 8 presents something of a learning curve. Material in Windows 7 that was automatically saved to 'my documents' now ends up--well, God knows where. I have to search around before I can find the PDF that I downloaded and have to use many times before I'm done with an assignment. Retrieval works best when the system is clear and easily comprehensible.
Don’t Use Windows XP, Windows Vista, or Disable TRIM
Does this apply to virtualized (hyper-v, VirtualBox, etc) instances that are HOSTED on SSD drives, as well?
Are you also saying we shouldn't run XP VMs on newer SSD Win8 machines (Surface pro?), even if we want full compatibility with older programs/games?
Just checked mine as I assumed it would be off by default, but it has been doing a weekly defrag for the last couple of months, since this PC was commissioned. I bought it complete without OS and installed an SSD then installed Win 7 64 bit straight to the SSD, yet it still enabled scheduled defrag, so don't assume it is off. Also just checked indexing and it was on as well, windows really should be smarter than that, but obviously these have to be checked for new installs as you can't assume windows gets it right.
next page →