catilley1092
Extraordinary Member
- Joined
- Nov 19, 2010
- Messages
- 1,063
Neemobeer, I agree that TRIM in itself needs no space to operate, yet there's something about these drives, when filled to a certain point (which may vary by source, even among SSD OEM's), performance goes downhill, that I know for sure. Maybe I've been reading at the wrong sites, many says that once the drive gets 'too full' (again, that varies by brand, some has 'hidden blocks') that TRIM can't do it's job effectively. Maybe this is confused with garbage collection (GC), which are two different services.
Some of the same sources also says that TRIM, as you've stated, marks data as invalid, yet recovery is still possible of some, especially on an overloaded SSD. I've used Recuva as a test to recover deleted data on these & have successfully recovered items weeks after deletion, performed by CCleaner prior to every shutdown. This is why on my three best computers, which are also used to make transactions, after repeated slow benchmarks across two days, will image the SSD (also performed weekly), secure erase then restore image, regardless if SATA-3 or NVMe SSD, performance increases. This I perform yearly (or when performance drops) & am not concerned about wearing, because the good models are tougher than spinners anyway, am on my oldest at the moment, a 128GB Crucial m4 purchased in 2012, still with 98% lifespan left, if SMART data is to be trusted, the same data shows the drive has been used only 4 months & 3 days.
Point being, if TRIM (& GC) does it's thing as supposed to, one wouldn't have to perform an SE to regain performance, especially on one in particular that uses less than 20% of available space (this one has since been upgraded to W10). Have used every trick was told on their forums, logged out & left running for 10-12 hours, booted into the UEFI or BIOS with only the power cable attached for the same amount of time (they say it forces an extended GC). Yet it seems like nothing cleans up the drives & restores lost performance like a SE does, have the latest Parted Magic, now needed for NVMe SSD's.
I've ran the small test that's supposed to show that TRIM is working, and checked via cmd that it's enabled, for the most part am satisfied. It's just that on the few smaller models with a higher percentage of data stored, I have to SE more often, as I don't believe TRIM is doing it's thing, or a combination of that & GC isn't as it should be. My drivers are usually always the latest available, in the proper AHCI mode, and in the case of a NVMe model, have the latest driver installed. Overall, I spend more time maintaining my computer collection than everything else I do in life combined, am always upgrading, tweaking, doing something to boost performance in some way. Just ordered a 256GB Samsung 850 Pro that's on promo at $109.99 at B&H Audio-Video (same price on Newegg/Amazon at this time), have zero idea where it's going at the moment, yet the one removed will be installed where needed the most, just as I do with GPU's when buying a new model. Two upgrades with one purchase. When one has a collection of 9 PC's alone (5 self-built), not to include half a dozen notebooks, prioritizing hardware is critical.
Of course, this is with Windows 7, if I pull the SSD & connect to a W10 (or 8.1) powered computer via eSATA port & run the manual TRIM a couple of times from the defrag window, this make a difference, cannot recover data afterwards. Nor on a Linux install, where TRIM has to be manually tweaked for best results, rather than the default weekly 'cron job' & there's a Terminal option, same function as cmd, where one can manually run it at anytime (sudo fstrim -v /) & the same for the /home partition if on the SSD by sudo fstrim -v /home. This is very effective & benchmarks before & after shows a difference. Unfortunately, as far as I know, there's no way to force this on Windows 7, other than stated above by removal & ran on a later OS manually, and really the only 'negative' I have in regards to the OS.
Maybe this is another one of those areas where a true SP2 could had made a difference, by the inclusion of the trimming feature for SSD's in the defrag option. Yet Microsoft was h*** bent on pouring cash (from W7 & Office 2010 sales) into a bottomless pit with W8 & later, 8.1, had they been spending as though a drunken sailor over Vista with profits from XP, would had been bankrupt before the W7 release. Earlier & later OS's did include new features with most every SP, although with W7, wasn't a lot added for most users, rather a repackage of previous updates for faster clean installs, as well as the pseudo SP2. Of course in the big picture, this takes nothing away from Windows 7, the first to have native support for SSD's, as well as other features, the greatest OS Microsoft ever released in the opinion of many
Cat
Some of the same sources also says that TRIM, as you've stated, marks data as invalid, yet recovery is still possible of some, especially on an overloaded SSD. I've used Recuva as a test to recover deleted data on these & have successfully recovered items weeks after deletion, performed by CCleaner prior to every shutdown. This is why on my three best computers, which are also used to make transactions, after repeated slow benchmarks across two days, will image the SSD (also performed weekly), secure erase then restore image, regardless if SATA-3 or NVMe SSD, performance increases. This I perform yearly (or when performance drops) & am not concerned about wearing, because the good models are tougher than spinners anyway, am on my oldest at the moment, a 128GB Crucial m4 purchased in 2012, still with 98% lifespan left, if SMART data is to be trusted, the same data shows the drive has been used only 4 months & 3 days.
Point being, if TRIM (& GC) does it's thing as supposed to, one wouldn't have to perform an SE to regain performance, especially on one in particular that uses less than 20% of available space (this one has since been upgraded to W10). Have used every trick was told on their forums, logged out & left running for 10-12 hours, booted into the UEFI or BIOS with only the power cable attached for the same amount of time (they say it forces an extended GC). Yet it seems like nothing cleans up the drives & restores lost performance like a SE does, have the latest Parted Magic, now needed for NVMe SSD's.
I've ran the small test that's supposed to show that TRIM is working, and checked via cmd that it's enabled, for the most part am satisfied. It's just that on the few smaller models with a higher percentage of data stored, I have to SE more often, as I don't believe TRIM is doing it's thing, or a combination of that & GC isn't as it should be. My drivers are usually always the latest available, in the proper AHCI mode, and in the case of a NVMe model, have the latest driver installed. Overall, I spend more time maintaining my computer collection than everything else I do in life combined, am always upgrading, tweaking, doing something to boost performance in some way. Just ordered a 256GB Samsung 850 Pro that's on promo at $109.99 at B&H Audio-Video (same price on Newegg/Amazon at this time), have zero idea where it's going at the moment, yet the one removed will be installed where needed the most, just as I do with GPU's when buying a new model. Two upgrades with one purchase. When one has a collection of 9 PC's alone (5 self-built), not to include half a dozen notebooks, prioritizing hardware is critical.
Of course, this is with Windows 7, if I pull the SSD & connect to a W10 (or 8.1) powered computer via eSATA port & run the manual TRIM a couple of times from the defrag window, this make a difference, cannot recover data afterwards. Nor on a Linux install, where TRIM has to be manually tweaked for best results, rather than the default weekly 'cron job' & there's a Terminal option, same function as cmd, where one can manually run it at anytime (sudo fstrim -v /) & the same for the /home partition if on the SSD by sudo fstrim -v /home. This is very effective & benchmarks before & after shows a difference. Unfortunately, as far as I know, there's no way to force this on Windows 7, other than stated above by removal & ran on a later OS manually, and really the only 'negative' I have in regards to the OS.
Maybe this is another one of those areas where a true SP2 could had made a difference, by the inclusion of the trimming feature for SSD's in the defrag option. Yet Microsoft was h*** bent on pouring cash (from W7 & Office 2010 sales) into a bottomless pit with W8 & later, 8.1, had they been spending as though a drunken sailor over Vista with profits from XP, would had been bankrupt before the W7 release. Earlier & later OS's did include new features with most every SP, although with W7, wasn't a lot added for most users, rather a repackage of previous updates for faster clean installs, as well as the pseudo SP2. Of course in the big picture, this takes nothing away from Windows 7, the first to have native support for SSD's, as well as other features, the greatest OS Microsoft ever released in the opinion of many
Cat
