Hi Harold, would you go into a little more detail on that.
My understanding, was to never defrag an SSD. A defrag can be damaging. Each cell in an SSD can only be written to so many times. There are algorithms in an SSD's controller that help to spread the data out over the entire drive so that you are not writing to the same cell over and over again while there are other cells that don't ever get written to.
A defrag is constantly reading and writing data to move it around the drive and can severely impact your wear leveling.
Is your's brand new info?
yeah, I seen this too that you should minimize writing to SSD's and never do defrag, but it's a fact that if a file is severely fragmented it will be slower, if the "window turn rate" is getting high, it means the kernel file system driver changes access paths to another location.... in a normal disk it's another physical location while on an ssd it's not... still it's another location....
Still would be interesting to see figures about these things.....
How about linux and ext3, ext4 file systems, every time you access a file it's being tagged to show the last access time, unless you flag the file system with "noatime", does that not create significant writes to the file system?
How about pagefile on an ssd disk, does that not create significant writes to the file system?
maybe you should never put a database on a system with ssd, there is so much writing to the logfiles, that it will kill the ssd
I had ssd's in my laptop's for quite many years now and never seen any of these issues....
Have to go, need another one: