Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Before adding solid-state drives, right-size your infrastructure using workload profiling

Len Rosenthal, Load DynamiX | Oct. 19, 2015
If you’re looking to add Solid-State Drives to your storage environment you want to avoid under-provisioning to ensure performance and scalability, but to meet cost goals and avoid unnecessary spending you need to avoid over-provisioning. Workload profiling can help you achieve the critical balance.

This vendor-written tech primer has been edited to eliminate product promotion, but readers should note it will likely favor the submitter’s approach.

If you’re looking to add Solid-State Drives to your storage environment you want to avoid under-provisioning to ensure performance and scalability, but to meet cost goals and avoid unnecessary spending you need to avoid over-provisioning. Workload profiling can help you achieve the critical balance.

A recent survey of 115 Global 500 companies by GatePoint Research and sponsored by Load DynamiX showed that 65% of storage architects say they are doing some sort of pre-deployment testing before making their investment decision.  Alarmingly, only 36% understand their application workload I/O profiles and performance requirements. They don’t know what workload profiling is and how it can be used to accurately evaluate vendors against the actual applications that will be running over their particular storage infrastructure.

Here’s how workload profiling can help reduce over-provisioning and under-provisioning of SSD storage investments.

What is workload profiling?

Workload profiles, often called I/O profiles, are data and statistics that directly relate to storage activity and loading in real (observed) production storage arrays. Workload profiles characterize the realistic, sometimes massive, application workloads that stress networked storage at an infrastructure level.  Profiles typically comprise a mix of virtualized applications, including databases, that can have significant random I/O content. I/O profiles contain information on reads vs. writes, the mix of random versus sequential data access, the data and metadata commands, file and directory structures and IOPs to name a few of the key metrics.

There are two key steps to creating a workload profile:

* Gather production data: To capture the data to create the workload model, the first step is to access the storage array logs and other statistics available from each of the production storage array’s proprietary tools. Every vendor has their own way of reporting storage I/O and utilization data and most storage admins know how to run these tools and utilities over a predetermined period of time. This data provides the foundation of the workload-to-performance relationship. And can be input into a storage workload modeling application.

* Workload Modeling: In the second step, we create the models based on the array data. There are commercially available tools that can take storage array log data and directly import it into the workload model. These models can then be used to vary the assumptions and perform a myriad of what-if and worst case scenarios. Such applications can maintain libraries of repeatable scenarios that can be used to stress a storage system under a realistic simulation of the workload(s) it will be supporting in production. Workload modeling enables the comprehensive performance testing of any flash or hybrid storage system under the actual conditions that it is expected to operate. With highly accurate simulations, storage performance can be fully predictable.

 

1  2  Next Page 

Sign up for CIO Asia eNewsletters.