http://www.monomachines.com/shop/intimus-crypto-1000-hard-dr... or you can get a service to come out and do it on site.
You get a write amp of 1 until the drive is filled the first time. After that, it's a function of
1) how full the drive is (from the drive's point of view—this is why TRIM was invented)
2) the over provisioning factor
3) usage patterns, such as how much static data there is
4) how good the SSD's algorithms are
5) other (should be) minor factors, such as wear leveling
Source: I used to be a SSD architect.
There have been attempts to use an SSD as a swap layer to implement SSD-backed
memory. This method degrades write performance and SSD lifetime with many small,
random writes. Similar issues occur when an SSD is simply mmaped.
To minimize the number of small, random writes, fatcache treats the SSD as a
log-structured object store. All writes are aggregated in memory and written to
the end of the circular log in batches - usually multiples of 1 MB.
ptr = mmap(..., len, ..)
/* do stuff with ptr */
Or do I just msync the whole region then hope and pray that the OS will do the right thing?
The whole point of this piece of software is to be smart about how and when it flushes data so it can minimize impact on the write counter.