Texas Memory Systems longs to seduce 'larger player'

RE: Not HP.

Well, one could point out that 3Par doesn't meet any of the criteria set and yet got bought by hp (before Dell could get their grubby mitts on them). And 3Par seems to be quite a success story for hp.

But I'm not convinced hp will buy TMS. I would have liked them to five or more years ago, but now I see them as more intent on putting flash into storage devices or in the server, not in standalone devices in front of the array like the old RamSan devices.

RE: TMS is El' Crapo

".....Look for chip level RAID across entire array, multiple controllers, hot swapable everything, wear leveling and avoiding that pesky Write Cliff Error....." <Sniff, sniff> Smells like feature sell to me! The "write cliff" is when an SSD is full and write performance drops off as the SSD controller has to search for free space on the "disk" to write to, often by recovering space from deleted items or looking for those free "extents" still available. But that is exactly what happens with ordinary spinning disk too, which is why you'll defragment your drives and run an OS with volume management software that recovers such space. Trying to pretend that Company A's devices don't suffer from the "write cliff" issue is trying to pretend their SSDs work in a different manner to all other SSDs - unlikely. The classis solution is to overprovision - e.g., present a 1GB SSD space as only 800MB so you have a buffer for all that shuffling around of the data and to cope with wear. All solutions I've seen from vendors that claim to avoid the write cliff are simply using software to shuffle data and hide the over-provisioning. Nothing revolutionary or even vaguely unique.