Brian, on 05 February 2010 - 02:13 PM, said:
It does act like w giant cache for the HDD.
After that it sets the read priority to the SSD.
They claim a 70% performance increase, but we'll see.
Well, yes and no.
From the product literature, the assumption seems to be that the SSD is the same size as the HDD. If that's not the case, then what happens?
Do you have any control over what data is copied to the HDD? Can you control whether the SSD only caches reads, writes, or either? Can you adjust the cache policy to more closely suit your application requirements? From what I read, the answer was "No", because the product automatically copies the HDD to the SSD and then redirects all reads and writes to the SSD, bypassing the HDD entirely.
My previous point was that I don't see any added value to using this product versus purchasing imaging software and a SSD separately, and it seems to me that you get more flexibility when purchasing separately.
What's the point of using this versus imaging the SSD with the data from the HDD? Using standard imaging tools, your HDD would be available to be redeployed after imaging. With this, it's not.
I don't think I'm being unduly critical here. I just honestly don't see the value proposition for this product. If you feel differently, please feel free to point out what you think I'm missing/overlooking.