Originally Posted by Condusiv
Diskeeper 12 editions (version 16) do support newer operating systems such as Windows 8, and Windows Server 2012 operating systems. SSDs once autodetected, are optimized through Diskeeper 12 technologies (HyperFast, IntelliWrite, and TRIM) which are not the approach of a traditional file defragmenter. This resolves the performance issue with SSDs which occurs during the write activities due to the erase penalty. I would recommend downloading Diskeeper 12 Professional or Server for workstation or Server.
How would a Diskeeper know the different SSD controllers' proprietary algorithm? How could it optimize a SSD without having any control of the LBA?
Edited by DuckieHo - 4/1/13 at 10:30am
SSDs start out really fast and then quickly start to lose their speed and over time become subject to corruption.
Performance degradation is relatively rare now with enough free space.
This has never been the cause of corruption for a properly operating controller
SSDs require that old data be erased before new data is written over it, rather than just writing over the old information like with hard drives. This doubles the wear and tear and can cause major issues.
Not quite, the issue is that NAND is written in pages but erased in blocks.
The principle issue is write speed degradation due to free space fragmentation. Small free spaces scattered across the SSD cause the file system to write a file in fragmented pieces to those small available free spaces. By doing so, it degrades write performance by as much as 80% to the solid state drive.
Wrong, file fragmentation INCREASES SSD performance due to multiple channels. The issue is that dirty pages in the blocks.
SSDs can only write so many times to the drive as they have a finite number of writes that they can perform. Due to the doubling effect of needing to read and erase before it can write again, SSDs undergo twice as much use.
Non-issue for consumers..... any 3rd party software can only increase wear.
As the SSD approaches its limit, more fragmentation and write errors occur, causing SSD slows. Write performance decreases proportionately as free space fragmentation increases. All SSDs will suffer from this problem at one point or another unless HyperFast is used to optimize the solid state drive.
No way a 3rd party external program can no this since the LBA mapping is done within (and only within) the controller