konc wrote on 2020-01-16, 07:03:
InjecTioN wrote on 2020-01-15, 17:10:
We'll just have to test it then. 😀 I mean, it's definitely worth it if it in fact works. If it's just a placebo effect we're talking about, it's quite useless. I haven't read into TRIM enough to know exactly how it works though, so I'll start with that to get some actual results.
Yeah no, I was just being polite. A program that clearly says 1. It doesn't have trim code 2. Only tries to trigger win7 to do it 3. "It assumes that your windows 7 trim is fully working" won't trim anything on an OS that doesn't have trim.
So the only thing the application does is that it just rapidly fils up the filesystem, on which the lack of free disk space triggers the trim command if supported by the OS and SSD. After the trim command has been triggered, it obviously removes the data again.
So it actually should be a placebo then. Would the filling up of the filesystem perhaps free up cells too, though? Or would this just be a helping to slow things down, as full drives (both SSD's and HDD's) will in fact slow things down.
I've been reading this yesterday, which is quite a clear explanation on how it's supposed to work when supported by OS and storage device.
As a sidestep: My tests, even though DMA was disabled, show that a full SSD could in fact impact the performance of the drive. I'm expecting enabling DMA on the SSD will show even clearer results. I'll just check that tonight to have definitive results and to at least have something useful to document here. 😆