FlashSystem 9100 with Epic Workloads

Epic Workloads This material will share information with you on why the FlashSystem 9100 is a suitable storage system for Epic workloads Measurement of the FlashSystem 9150 with Epic has been performed with favourable results A FlashSystem 9100 with Epic blue print has been updated and is available on the redbook site here

Performance Measured FlashSystem 9100 Epic workload IBM FlashCore Modules deliver high performance with low latency Over 1M IOPS 4k read cache miss Inline hardware compression consistently ensures sub 1ms response FlashSystem 9100 bandwidth Up to 34GB/s possible to the host, with ~40GB/s internal bandwidth Ability to process host workloads as well as dealing with copy services and RAID rebuild operations Measured FlashSystem 9100 Epic workload 210k IOPS without snapshot 105k IOPS during 45 minute snapshot By comparison Pure claim a 175k with an X70 – a machine that is comparable to a FlashSystem 9150

Scalability Scale the solution with the workload … … Grow with the workload overtime Clustering allows linear performance scaling Each additional 9100 has the bandwidth and capacity for 24 more FlashCore Modules Another 800TB effective Up to another 1M IOPS, and to 34GB/s Use a clustered pair of 9150s to compete against Pure X90 Or SAS expansion allows more storage with no further performance increase

FlashSystem 9100 has 99.9999% proven availability DRAID6 with FCM technology proactively identifies and repairs errors without impacting workloads FlashSystem 9100 has 99.9999% proven availability 100% availability guarantee with HyperSwap configurations installed by Lab Services engagement

Copy on Write or Redirect on Write? Copy on Write takes a copy of the data and moves it to the snapshot for the written extent. Although this causes some IO amplification to preserve the existing data before updating it with the new data, there is ample bandwidth available within the FlashSystem 9100 to perform this CPU efficient operation Redirect on Write causes metadata manipulation to allow the new copy of the data to be written to free storage without having to preserve the old copy first. Although this takes less throughput, it may require IO of metadata, and CPU usage to manipulate metadata Redirect on Write is not required for Epic workloads to have good performance!