* Posts by Shachar Fienblit

1 post • joined 4 Oct 2012

Kaminario's K2 data-gobbling champ squeezes out 2 million IOPS

Shachar Fienblit

Performance is serious business, not a game

The comments written by Violin’s CTO mix apples and oranges from multiple benchmark data points resulting in false conclusions. Let me clearly and factually present the truth.

First, Kaminario did two different benchmarks: an audited SPC-1 benchmark designed to give customers an apples to apples comparison of vendor performance with an industry standard workload, and a second benchmark based on an IOmeter-based random read only workload identical to what Violin promoted at VMworld.

SPC-1, as the market knows, is a well-defined benchmark and has a very high write component (2/3). The result from that benchmark was 1.2M SPC-1 IOPS at a cost of $0.40 per SPC-1 IOP. World records! Clear, factual, audited. Violin is welcome to join us in the peer review of SPC-1 and do the benchmark.

The second benchmark was a random read only workload identical to Violin’s 1.35M IOPS announcement. The difference is we used a single all MLC K2 system and they used two 6600 SLC based systems (as published in their report they measured 750K IOPS on a single system). Our result was 2M random read IOPS to their 750K. Our latency was 0.9 milliseconds (on the host) vs. 3.44 milliseconds in Violin’s benchmark report. Also in the report, they mention 4GBs throughput out of a single SLC 6600 (or 2GBs on their MLC systems) vs. 20GBs in our all MLC system. I am not sure why all of this confuses them. It’s again, clear, concise, and factual. Cheaper Flash, far better performance, single system.

Let me also address Violin’s misconception of our linear scale-out architecture. The K2 is a single system no matter how much capacity you put in it. Start small and grow. It scales out! It’s still a single system, because:

-- Volumes always span the entire address space, across all k-nodes

-- When adding capacity (non-disruptively) the system redistributes the volumes across the entire system automatically

-- The K2 has a single management application and full access to all the address space from any access point

-- It does its own automatic load balancing and does not rely on the application to do that for it

-- It has less overhead since you don’t save hot spares for each system (much better TCO)

Violin wants you to count the number of components in our system. A car has 4 doors, 4 wheels, 5 seats, pipes and cables, a few pistons, a radio and that cute little Hawaiian girl on a spring dancing on the dashboard – it’s still just one car.

Finally, performance is important but the real issue for all flash storage is enterprise capabilities. K2 provides end-to-end, self-healing high availability and fast, high-volume data protection, including N+1 redundancy, automatic failover, high-volume snapshots and hot-swappable components for fast, easy and non-disruptive operations all designed from the ground up for SSDs. With Violin, can customers trust 3rd party snapshots that were not designed for flash? Can customers trust Violin in replacing a VIMM while their live system is running a mission critical application?

We invite customers to seriously measure the performance and capabilities of each of us. Then they can decide who is playing games and who is serious about enterprise storage.

Shachar Fienblit, Kaminario VP of Engineering

1
0

Forums