Re: block sizes matter
It's obvious you're a Pure employee because your comment was terrible and makes no sense. Infinidat clearly used the same block size/workload across all three arrays. Just because Pure markets 32K block size doesn't mean they actually use it. Pure markets a lot of things it doesn't do. Why would this be any different? In fact, this isn't even the first publicly released benchmark that's exposed how poorly Pure performs.
In fact everyone is missing a very important point in all of this: Infinidat KNEW that they could take advantage of Pure & Unity because they know, what most actual technologists know, both of those architectures are single node, CPU bound, based architectures.
Of course Infinidat's results are "rigged" in their favor. XtremIO did the same thing with its bogus VD Bench script. Of course Infinidat highlighted what their system could do. But that doesn't explain why Pure & Unity performed so poorly.
Think about it. Why didn't they test a VMAX 250? Could it be because they knew that the VMAX 250--which is also marketed as a "midrange" array--wouldn't suck? Why not a 3PAR? Or an HDS F400/F600?
They picked these two systems because they knew these systems are popular but both are highly overrated. Even if Infinidat could outperform an HDS or a VMAX or a 3PAR, the results would be MUCH closer than this and wouldn't be enough to differentiate it this way.