according to the tech specs the OWC SSD will be connected using only 2 PCIe lanes. not impressed at all. plus, the SandForce controller is a no-go in my book. also I expect that the OWC SSD won't support native TRIM for OS X.
I totally missed this, the first read through... This thing is DOA at half the asking price.
I'd rather have the sand force controller as its garbage collection is good-enough that you don't need trim. Personally I hate trim. It's an abortion of a solution and having the drive just take care of itself without software support is my preference.
Saying you hate TRIM is like saying you hate to have your system run optimally. TRIM is very important - especially in heavy I/O situations, after a drive has been in service for a period of time, or if it's nearing it's capacity.
Also, there are several issues with Sandforce controllers:
First off, they rely on compression to achieve their performance. Incompressible data like media files (ZIP, RAR, audio, videos, and images) which are already stored in some compressed format, don't offer nearly the same performance.
Second, they can get into a degraded performance state in the absence of TRIM. There is only so much GC can do without knowing what data to preserve and what to discard. In heavy workload conditions, TRIM is essential on any drive.
Third, they don't work well with TRIM.
Fourth, they have notoriously premature failure rates. No other drive has the same record of premature failure as SandForce.
You should really read this article...
http://www.anandtech.com/show/6107/corsair-force-series-gs-240gb-review
There are MUCH better choices out there than SandForce and it's been this way for a few years now.
I guess that we're polar opposites on TRIM.
TRIM is an elegant solution to the problem that SSDs have with trying to figure out which data is valid. Add a simple IO control call so that when the filesystem marks a section of disk space as "free", it can relay that information to the disk via a TRIM command.
Works fine on Linux and Windows - the drive reports during initialization that it supports TRIM, and the OS enables the extra IO call in the filesystem.
It's only a mess on Apples, because Apple OSX doesn't use the industry standard APIs to ask the drive if it supports TRIM.
+1... and thankfully we have TRIM Enabler to make up for Apple's nonsense.