Controlling performance in the cloud: taking charge of your hosting environment

Controlling performance in the cloud:Taking charge of your hosting environment

www.databarracks.com | 2

Agenda

• Introducing: Databarracks and SolidFire

• High performance applications in a hosting environment: Historical challenges

• The language of performance – IOPS, Queue Depth, IOPS per Disk, IOPS per Application and calculating IOPS

• What key applications can now take advantage of flash performance in the cloud?

• Q & A

www.databarracks.com | 3www.databarracks.com | 3

Speaker Bio’s

• Stuart Oliver, Senior Service Provider Program Manager, SolidFire

• Currently the Senior Service Provider Program Manager at SolidFire where he is responsible for articulating SolidFire's value proposition to hosting service providers globally.

• Spent over 19 years in executive I.T. Management, Product Management and Product Marketing roles.

• Born in U.K. then emigrated to Canada and now currently lives in Colorado U.S.A.

• James Watts, Head of Marketing, Databarracks


Prize draw – stick around!

Stay until the end of today’s webinar, where we’ll be giving away a 256GB Solid State Drive worth £200.

Fill out the brief poll later on to be entered into a draw to win a Sphero Ball worth £100.

Winners revealed after Q&A!

67% Of all

workloads will be run in the

cloud by 2016


The Cloud Evolution

High

Med

Low

IOPS

ApplicationsTest / DevelopmentBackup / ArchiveStartups

Cloud today

Cloud 1.0

Cloud 2.0

Performance Sensitive AppsOracle / SAP / Private CloudHadoop / NoSQLMS Exchange, VDIERP,CRM

Cloud Evolution

$$$

$$

$

• High Performance

• QoS / Hard SLAs• Massive scale• Reliability• Security

Early cloud


Why don’t you run performance apps in the cloud?

• Current storage architectures delivers inconsistent and

variable performance (‘noisy neighbour’ effect)

• Inability to efficiently scale performance

• Unable to throttle performance independent of capacity

• Low levels of transparency (no visibility into systems)

• Dedicated storage array costs are prohibitive

• Perception of unreliability


Eliminating Noisy Neighbours

The Noisy Neighbour Effect Individual tenant impacts other applications

Unsuitable for performance sensitive apps

Quality of Service in Practice Create fine-grained tiers of performance

Application performance is isolated

Performance SLAs enforced

Noisy Neighbour Tier 0

Tier 1

Tier 2

Tier 3

Decreased Performance


Enterprise IT lacks storage agility, and is under significant pressure

• Deploy new applications and capabilities faster

• Provide more agile and scalable infrastructure

• Increase application performance and predictability

• Enable automation and end-user self-service

• Raise operational efficiency and reduce cost


Traditional enterprise storage falls short of these requirements

xDeploy new applications and capabilities faster

xProvide more agile and scalable infrastructure

xIncrease application performance and predictability

xEnable automation and end-user self-service

xRaise operational efficiency and reduce cost


xDeploy new applications and capabilities faster

xProvide more agile and scalable infrastructure

xIncrease application performance and predictability

xEnable automation and end-user self-service

xRaise operational efficiency and reduce cost

Enterprises are looking to service providers that can solve these problems


Why is understanding application IOPS Important?

The way an application operates will determine the workload it

generates

Caching and disk reads and writes all have an effect on how the

application creates load on a system

In legacy multi-tenant clouds the workloads can be very random

with many

different applications generating completely random I/O’s on the

system.

The random I/O’s cause very unpredictable performance to the

tenants using the shared cloud platform. The bigger the cloud

implementation the bigger the problem.

One of the primary reasons that the cloud has been primarily used

for test/dev or less critical applications is the unpredictability of

storage resource availability

I.T. simple can’t risk running key business applications in these

highly unpredictable cloud environments.


Understandingthe Language of Performance

Key Concepts – IOPS (Input/Output

Operations Per Second)

• I/O (Input / Output) – The process of writing

data to the disk or reading data from the disk

• The specific number of IOPS possible in any

system will vary greatly depending on

architecture



Key Concepts – IOPS per disk type

Device Type IOPS

7,200 rpm SATA drives HDD ~75-100 IOPS

10,000 rpm SATA drives HDD ~125-150 IOPS

10,000 rpm SAS drives HDD ~140 IOPS

15,000 rpm SAS drives HDD ~175-210 IOPS

Good Quality SSD SSD ~ 5,000 IOPS



Key Concepts – IOPS per Application

Use CaseLow Performance Instance

(IOPS)Med Performance Instance

(IOPS)High Performance Instance

(IOPS) Est. Read %

MS SQL Server VM 1000 3000 10000 80

MySQL Server VM 1000 3000 10000 80Oracle 11G 1000 3000 10000 80SAP 1000 3000 10000 80Hadoop 1000 3000 10000 80Mongo DB 1000 3000 10000 80Cassandra 1000 3000 10000 80

Web Server VM (windows) 100 300 700 95

Web Server VM (linux) 100 300 700 95VDI (Windows) 20 50 150 40VDI (Linux) 20 50 150 40Dev Server VM 100 300 1000 50Application VM 500 1000 2000 90



Key Concepts – Queue Depth

• A spinning disk can only serve a single IO at a time,

and any seek between IOs adds significant latency.

• In cloud environments where multiple applications or

virtual machines share disks, unpredictable queue IO

to a single head can easily result in orders of

magnitude variance in latency, from 5ms with no

contention to 50ms or more on a busy disk.http://www.tomshardware.com/reviews/ssd-gaming-performance,2991-3.html




Queue depth refers to the number of outstanding access operations. In the picture above, each solid line represents one disk operation, which can be either a read or write. Because three operations overlap in the same period, there’s a queue depth of three.

http://www.tomshardware.com/reviews/ssd-gaming-performance,2991-3.html




• Compared to the single-IO bottleneck of disk, SSDs

have eight to 16 channels to serve IOs in parallel,

and each IO is completed quickly.

• So even at a high queue depth, the variance in

latency for an individual IO is low.

• This is the primary reason that you cannot

guarantee storage performance on a spinning disk

architecture.

http://www.tomshardware.com/reviews/ssd-gaming-performance,2991-3.html


SSD is ideal for:

• Performance oriented relational databases (MSSQL or MySQL)

• Large VDI (Virtual Desktop Infrastructure) implementations

• Large virtualized corporate (private) cloud environments

• Intensive analytics applications

• Heavy SAP/Oracle/MongoDB/Hadoop/ERP/CRM implementations

• Online Gaming and multimedia configurations


5 essential questions when choosing performance storage

• Can you guarantee storage quality of service for

my critical server?

• Can you guarantee IOPS to my critical server?

• If needed, can I add IOPS without changing my

volume size or migrating my data?

• Can you guarantee that I will not have a noisy

neighbour problem?

• Can you offer me an SLA on storage performance?


Summary

Recommendations

• Save money: You don’t need to overprovision for

the high watermark or worst case scenario

anymore

• Take the time to understand what the IOPS

requirements of applications

• Don’t buy expensive flash appliances when you

can simply provision only what you need from

Databarracks

Questions?

Stay until the end for entry into the prize draw!


Winner Announcements

SSD Winner is: Sphero Winner is:

Controlling performance in the cloud: taking charge of your hosting environment

Technology

Transcript of Controlling performance in the cloud: taking charge of your hosting environment