- Aug 25, 2001
- 56,587
- 10,225
- 126
Just wondering.
I mean, I know that SF achieves its superlative write amplification by using compression, and with software FDE, the sectors that are written to the drive are basically uncompressable, so that's a worst-case scenario for the drive.
What I'm curious about, is if it causes the data written to the drive to actually expand, larger than the source data? I know that this is true with many compression algorithms, they optimize for the main case of compressability, with the sacrifice that if the data is incompressable, it actually gets larger when output from the compression algorithm.
If so, doesn't that mean that I'm encroaching the reserved spare area with user data, that proved to be incompressable/expand larger than the user data sectors? Will this cause problems with SF's algorithms?
Anyone have any first-hand experience with this?
I did notice that drive speed was noticeably slower in CDM, after the FDE was finished.
I mean, I know that SF achieves its superlative write amplification by using compression, and with software FDE, the sectors that are written to the drive are basically uncompressable, so that's a worst-case scenario for the drive.
What I'm curious about, is if it causes the data written to the drive to actually expand, larger than the source data? I know that this is true with many compression algorithms, they optimize for the main case of compressability, with the sacrifice that if the data is incompressable, it actually gets larger when output from the compression algorithm.
If so, doesn't that mean that I'm encroaching the reserved spare area with user data, that proved to be incompressable/expand larger than the user data sectors? Will this cause problems with SF's algorithms?
Anyone have any first-hand experience with this?
I did notice that drive speed was noticeably slower in CDM, after the FDE was finished.
