
John Furrier7





What is the difference and why should any care about All Flash Arrays vs Hybrid Arrays? CIOs want to know this. I get asked this a ton.. thoughts?

Dave Vellante

all flash is the race car whereas hyrids are the souped up production vehicle

Stuart Miniman I think your analogy works for adding flash to older arrays (tier-1 hybrid), but not newer unified hybrids which have been built for flash+disk w higher % of flash

David Floyer If you have to go to disk, you have high IO variance. Database performance is determined by locking rate, and low IO latency AND low IO RT variance are key metrics.

David Floyer

All flash arrays have lower consistent latency - the variance of the IO in a well designed all-flash array is always very low. In hybrid systems some of the IO comes from disk - by design the variance is high. High activity DBs love low variance.

Dave Vellante so is it correct that hybrids can go after a broader set of use cases and if so which is a bigger market?

David Floyer The broader market at the moment is supporting existing applications. The higher value market of the future is supporting emerging applications.

Jean-Luc Chatelain
At the end of the day, the how is less relevant that the what. CIO will care for technology which gives best $/GB/s and best $/IO/s because workloads have varied profiles

David Floyer Hi Jean-Luc - That is true for many applications. For some very high business value application low latency will be an imperative. Designing a flat database where all functions can operate in parallel has very high business value.

Jean-Luc Chatelain
@dvellante I respectfully disagree on your car analogy. It is only a matter of the design of the hybrid. Posche Cayenne is a 4WD with the heart of a sports car and same can be done for hybrid arrays.

Dave Vellante I would agree re: the Cayenne - I would argue the F1 is purpose built for a more narrow use case (i.e. all flash for DB)

Jean-Luc Chatelain
@dvellante Dloyer calls its xflash, I call it IME (Infinite Memory Engine) but yes in the end it is about giving a memory semantic and hide the ugliness of disk protocols and limitations

Dave Vellante so how will this infinite memory pool change application design?

Jean-Luc Chatelain
@dvellante It does not change designs but it evolves with the app. If app is uses file/block semantic, it looks like file/block but if app is true in-memory then it uses a memory semantic mmap() for example

Dave Vellante what % of today's apps are written with a memory-dominated semantic in your est. and how will this change over time?