The good people at Texas Memory Systems read StorageMojo.com and at my invitation offered this response to my post An SSD For The Rest Of Us. I think they did a pretty good job of laying out the, IMHO, historically under-appreciated RAM SSD. Naturally I have a couple of comments at the end.
*Dear Storage Mojo:*
*We are excited to see solid state disks get some coverage in your blog even if we might have different ideas about the DDR RAM solid state disk market.*
First, we like flash memory too. We like that it has high density and is non-volatile. It provides a great storage media for USB drives, cameras and even iPods. We would even want one in a notebook so that it will survive the fall a hard drive cannot, and the low power usage really adds value when you are running on batteries. The fact that all of these industries have adopted flash has led to a big drop in its price. The success of flash has cost someone some business… hard disk companies making microdrives. Interestingly, we have yet to feel any competitive pain from flash drive manufacturers.
It is worth pointing out that companies have been promoting flash memory systems for commercial business applications for years. Their prices have always been lower, their densities higher and they have always been non-volatile. Inspite of these factors, none of these companies have traction in the enterprise applications area that we sell into.
Why is that? Flash disks use flash memory and flash memory has some inherent limiting characteristics:
- it’s write speed is poor (comparable to disks)
- inspite of the best efforts of the industry it is still easy to wear out the write cycles, and finally
- the read speed is still a lot slower than our read speed
As an addendum to this note, we have included a description of the hard work a flash drive has to do just to get a write done.
Compare the performance specifications of the Samsung flash drive to the RamSan system:
RamSan peak IOPS: 400,000 (read or write, random or sequential)*
Samsung peak IOPS: 2,200 (Webserver IOmeter pattern) (reads only). Note that for the Database pattern it is actually lower then most single hard disks (~85 IOPS).
A flash disk in a notebook is hardly likely to wear out the write cycles from operating system boots and the occasional save of a document, but that same disk in an enterprise storage system will wear out well before the ROI is realized. If we could write 400,000 IOPS to a flash drive (which we can’t because they are way too slow) it would take us seconds to wear out the drive).
Flash systems will inevitably gain traction with the lower end of the solid state disk market but as the last few years have shown we are not really stealing market share from each other as much as we are both growing our respective markets. The flash drive companies are growing and the intensity of that market is reflected in the pace of acquisitions. Independently, Texas Memory Systems has grown its DDR RAM solid state disk market over 50% this year. The future of our combined markets has never been stronger.
Regards,
Texas Memory Systems
The StorageMojo take
TMS makes a number of good points. The most powerful, IMHO, is that their RAM SSD is a big honking fast machine. Stick 8 FC ports on one and you might actually come close to those 400,000 IOPS. There really is no substitute for a big RAM SSD if that is what you need. TMS is focused on the high-end and flash is not a threat there – today.
On the other hand I detect a bit of whistling past the graveyard bravado in the TMS reply. When a product comes along on the steep downward pricing curve that flash has – much faster than disk or even RAM – that offers some of your significant advantages – non-volatility, good performance (for some apps) relative to disks – at a fraction of the cost, you have to think hard about the possibility of substitute architectures emerging.
Conjecturally, such an architecture might replace the implicit centralized schema of the TMS FC products with a distributed, shared-nothing plan. Local attach is both faster and cheaper, so if a web server farm of pizza boxes were equipped with flash SSDs, one might see a sizable fraction of TMS performance at a much lower cost without the FC management headaches. Other, less obvious, options no doubt will be invented.
Once people see a much cheaper alternative to RAM SSDs, the juices start flowing and inventions occur. If I were TMS, I’d ask a couple of my better engineers to work part time on creative flash-based SSD architectures. Somebody will, it might as well be you.
Robin,
Texas Memory SSD is perfect for high speed recording of internet ‘backbone’ traffic (security) or similar applications where speed is the #1 requirement and the cost becomes a secondary issue.
In a typical HA solution the cost will double, as this product is a ‘single point of failure’ and replication is required.
Not every enterprise is ready to trade redundancy, failover and price point for speed!
While there are some places where high speed is needed, in most cases a distributed cluster solution is a much better choice.
Google is a proof – how with cheap computers and distributed FS one can build the fastest search in the world – without using fancy storage.
Everything fails sooner or later – nothing is ‘rock solid’ says Google…
Now, if Sun can make the ZFS cluster capable/distributed… 🙂
Every time when a sales manager is explaining to me how ‘rock solid’ solution centralized storage is, I can’t stop thinking about Titanic…
Is a TMS really an SPOF? Sure, disaster, but they are very redundant along the lines of power and so on. I am testing my old Imperial Megaram 5000 (8port 1Gb FC Solid State) side by side against the modern TMS and I’ll say that it is much better than just the simple 1Gb->2Gb expectation…
Also, TMS resells PolyServe in which case is it quite simple to make a clustered NAS in front of TMS to provision direct I/O NFS access over, say, triple bonded GbE to serve as an “accelerator” if you will for transaction logs or temp sorting space…all without the connectivity and provisioning difficulty associated with FCP. It is an interesting approach to getting some SSD to a lot of servers–sans LUN masking and switch zoning…
I think I’ve blogged that one at http://kevinclosson.wordpress.com/
classical example of disruption at work – and there is no question who will eat who’s lunch later 😉
Flash has the advantage in size but what if my whole DB fits in a few GB? I can get a small DDR based system (hyperdrive) for a fraction of the cost of the TMS beasts.
Also, considering the typical replication setup wouldn’t flash’s poor write performance cease to be an issue? Just take it out of the list of available servers while you do the update. I’m just guessing but wouldn’t the random read IOPS more than make up for the fact that write sucks?
Maybe a cheap RAM based Hyperdrive4 as the master that handles writes and a bunch of flash drives on the slaves.