Chosen Solution
Wow. That title had a lot of acronyms. ANYWAY, So I’ve been wondering, is indexing on an SSD a good idea? any performance gained or lost by doing so? and is it a bad idea to index the WHOLE Computer? @avanteguarde @danj also, @evan where did my windows 10 category go? I don’t see it in the selection anymore.
By “Indexing Files”, what you really mean is Windows has a giant database that tells the operating system where each file location is in the file system. This giant database is organized and updated by the Windows Search service. “Indexing” means the database is organized by a certain field so that the way you try to find something on a computer is faster. https://en.wikipedia.org/wiki/Database_i… Not sure why an SSD would be harmed by this, considering it is simply a file, and TRIM would keep used/unused SSD cells from immature deterioration.
It’s not good for the SSD long term, kinda like fragmenting. It will still search faster, but it will degrade the lifespan by an amount, but it really doesn’t matter either way. Personally, I indexed my SSD. It’s your choice. Hope that helped!
The Indexing you are speaking about is really useful for a server or cache server which is storing web pages. It’s not very useful for a client system. As for using a SSD to store them (it makes no difference what the I/O is) the churn of the data is what will wear the SSD. So if the the web pages are static in nature or change lets say daily the amount of change is not that heavy. Its if you were to monitor something like the stock market which has trades going every 10 sec’s or so that the churn would wear the drive. Even still the number of stocks would need to be quite high as well. Now lets look at a shared database (DB2/SQL/Sybase) used in a store which manages large quantities of goods then the index would help keep the counts correct to the second. Some of these DB’s do their own indexing and some may even use the MS developer code to setup the index function.
