TMS tries to tarnish IBM Quicksilver pitch
Devil is in the detail #
Posted Thursday 30th October 2008 11:19 GMT
While I knew this box was coming from Woody and co at TMS, and in principle the concept is similar at a high level to what we demo'd as Quicksilver, in this case the 1M comparison is not apples for apples.
Our 1M IOPs was run with a mixed 70/30 ratio of reads and writes at 4K blocks. We all know that writes are the problem child for flash, and in some cases mixed workloads are even worse.
The TMS spec sheets don't give anything other than 100% read numbers, and doesn;t qualify at what transfer size.
If we take this at face value, and assume its small blocks 512byte or 1K, then the real number to compare this against Quicksilver would be 4.7Million IOPs. That is, if we had quote pure read numbers for Quicksilver. That would however have needed more SVC nodes, and several more fully populated Power Systems 595 hosts...
I'd like to see the 'details' - as I'm interested what the RamSan can do with a more realistic real-life workload.
Popular Whitepapers
- Enterprise PBX buyer's guide
Access to expert research on all aspects of the IP PBX market - Checklist: Midmarket ERP Solutions
Control your rising business costs - Ensuring high service levels in cloud computing
Keys to effective service management - GPFS Sequential I/O performance
IBM BladeCenter and IBM System Storage - Managing desktop software for fun and profit
On-demand webcast - Analyst Keynote: The Register Agile Data Center Summit
On-Demand: Audio Only