Re: TRIM for SSD when SSD set as a cache
Posted: Thu Sep 15, 2022 3:14 pm
Thank you offering help. But I really am quite aware of all configuration options and documentation. I've spent 2 days analysing the issue and possible causes.
I would appreciate a honest answer regarding the question if TRIM support is still planned and when to expect it.
I also typed a detailed answer explaining the tests I made, but somehow the post is gone and I'm to busy/lazy to retype it.
Let's just say that the results are conclusive.
This is the short version:
Basically the same scenario writing to the ssd does not choke it's write speed when using NTFS with TRIM. Also wiping the ssd with a secure erase alleviates the problem as Primocache L2 drive for a few write cycles till the data amount written passes the drives capacity. Overprovisioning the ssd by 50%, meaning leaving half the capacity unpartitioned and 50% of the capacity as L2 cache, also solves the problem and the write throughput stays steady.
I would appreciate a honest answer regarding the question if TRIM support is still planned and when to expect it.
I also typed a detailed answer explaining the tests I made, but somehow the post is gone and I'm to busy/lazy to retype it.
Let's just say that the results are conclusive.
This is the short version:
Basically the same scenario writing to the ssd does not choke it's write speed when using NTFS with TRIM. Also wiping the ssd with a secure erase alleviates the problem as Primocache L2 drive for a few write cycles till the data amount written passes the drives capacity. Overprovisioning the ssd by 50%, meaning leaving half the capacity unpartitioned and 50% of the capacity as L2 cache, also solves the problem and the write throughput stays steady.
