SPM User Guide

8/10/2019 SPM User Guide

1/50

3333333333

System Performance Modeler 1.5

User Guide

NetApp, Inc.

495 East Java DriveSunnyvale, CA 94089

U.S.

Telephone: +1(408) 822-6000Fax: +1(408) 822-4501

Support telephone: +1 (888) 463-8277

Web:www.netapp.comFeedback: [email protected]

Part number: 215-09069_A0May 2014
http://www.netapp.com/http://www.netapp.com/


2/50

Copyright Information

Copyright 19942014 NetApp, Inc. All rights reserved. Printed in the U.S

No part of this document covered by copyright may be reproduced in any form or by any meansgraphic,electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrievalsystemwithout prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY

AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENTSHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice. NetAppassumes no responsibility or liability arising from the use of products described herein, except as expresslyagreed to in writing by NetApp. The use or purchase of this product does not convey a license under anypatent rights, trademark rights, or any other intellectual property rights of NetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents, orpending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictionsas set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause atDFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark Information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch, ASUP,AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign Express, ComplianceClock,Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio,Engenio logo, E-Stack, FAServer, FastStak, FilerView, FlexCache, FlexClone, FlexPod, FlexScale,FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache,NOW (NetApp on the Web), Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP,ReplicatorX, SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, ShadowTape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapIntegrator,SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot,SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and

XBB are trademarks or registered trademarks of NetApp, Inc. in the United States, other countries, or both.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United States and/or othercountries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation inthe United States and/or other countries. RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, andRealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are trademarks ofRealNetworks, Inc. in the United States and/or other countries.

All other brands or products are trademarks or registered trademarks of their respective holders and shouldbe treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.


3/50

System Performance Modeler User Guide 3 of 50

Table of Contents

INTRODUCTION TO SYSTEM PERFORMANCE MODELER................................................................................. 511.1 What SPM does................................................................................................................................................... 51.2 Features in SPM.................................................................................................................................................. 6

SPM QUICK START............................................................ .............................................................. ....................... 722.1 Use cases............................................................................................................................................................ 7

New system deployment ........................................................ ............................................................... ............ 7

2.1.1 What if ............................................................... .............................................................. .................................. 72.1.2 Consolidation ............................................................... .............................................................. ....................... 72.1.3 Maximum system performance ......................................................... ............................................................... . 72.1.4

2.2 Performing a new forward sizing....................................................... ............................................................... . 8

Detailed inputs ............................................................. .............................................................. ..................... 112.2.1 Advanced options ........................................................ .............................................................. ..................... 132.2.2

2.3 Importing workload from AutoSupport........................................................................................................... 142.4 Importing from custom app workloads........................................................ ................................................... 152.5 Performing a new reverse sizing....................................................... .............................................................. 16

SIZING WITH FLASH CACHE AND FLASH POOL ACCELERATION................................................................. 2233.1 Changes to user interface....................................................... ............................................................... .......... 223.2 Creation of aggregates enabled by flash pool................................................................................................ 233.3 Flash output changes.............................................................. ............................................................... .......... 23

IMPORTING WORKLOAD INFORMATION........................................................................................................... 25

44.1 Perfstat...................................................... ................................................................. ........................................ 25

USING THE WORKLOAD MODULES................................................................................................................... 295

5.1 Virtual desktop infrastructure module................................................................................................ ............ 295.2 Microsoft exchange 2007 module................................................................ .................................................... 315.3 Microsoft exchange 2010/2013 calculator import module........................................................ ..................... 315.4 SMB 1.0 CIFS home directories module......................................................................................................... 325.5 SMB 2.x/3.0 CIFS home directories module................................................................................................... 335.6 Database applications module......................................................................................................................... 345.7 Custom application module................................................................................................................... .......... 36

ADDITIONAL SIZING OPTIONS.............................................................. .............................................................. 3966.1 Layout options.................................................................................................................................................. 39

6.2 SnapMirror options........................................................ .............................................................. ..................... 40

6.3

System generated intermediate workloads.......................................................................................... .......... 41

UNDERSTANDING SPM SIZING OUTPUT........................................................................................................... 43

7

7.1 Suggested configuration and layout............................................................ ................................................... 437.2 Layout recommendations................................................................................................................................ 437.3 Controller/Node perspective system utilization............................................................................................. 447.4 Drive calculations and flash pool.......................................................................................................... .......... 457.5 Adjustments for drives and other outputs.............................................................. ........................................ 457.6 Node increment details............................................................ ............................................................... .......... 467.7 Inputs section...................................................... .............................................................. ................................ 467.8 Failed configurations section.......................................................................................................................... 467.9 Reverse sizing report............................................................... ............................................................... .......... 47

ADDITIONAL RESOURCES.................................................................................................................................. 488

VERSION HISTORY............................................................ .............................................................. ..................... 499


4/50


Preface

This document describes how to perform sizing for NetApp FAS systems.

AUDIENCE

The primary audience for this document is technical personnel such as systems administrators,engineers, professional services engineers, and professional services consultants at NetApp.

KEYBOARD AND FORMATTING CONVENTIONS

You can use your product more effectively when you understand how this document uses keyboardand formatting conventions to present information.

Keyboard conventions

Convention What it means

Enter, enter Used to refer to the key that generates a carriage return; the key is namedReturn on some keyboards.

Used to mean pressing one or more keys on the keyboard and then pressingthe Enter key, or clicking in a field in a graphical interface and then typinginformation into the field.

Formatting conventions

Convention What it means

Italicfont Words or characters that require special attention.

UI literals.

Placeholders for information that you must supply.

For example, if the guide says to enter the arp -d host name command,

you enter the characters "arp -d" followed by the actual name of the host.

Monospaced font Command names, option names, and daemon names.

Information displayed on the system console or other computer monitors.

Contents of files.

File, path, and directory names.Bold

monospacedfontWords or characters you type. What you type is always shown in lowercaseletters; unless your program is case-sensitive and uppercase letters are necessaryfor it to work properly.

SPECIAL MESSAGES

This document might contain the following types of messages to alert you to conditions you must beaware of.

Note: A note contains important information that helps you install or operate the system efficiently.

HOW TO SEND YOUR COMMENTS

You can help us to improve the quality of our documentation by sending us your feedback.

Your feedback is important in helping us provide the most accurate and high-quality information.

If you have suggestions for improving this document, send us your comments by e-mail [email protected] help us direct your comments to the correct division, include the nameof your product in the subject line.

DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

Abbreviation/Phrase Explanation/ Definition

SPM System Performance Modeler

CSI Common Sizing Infrastructure

ASUP AutoSupport
mailto:[email protected]:[email protected]:[email protected]


5/50


Introduction to System Performance Modeler1

System performance modeler (SPM) is NetApps next-generation performance sizing tool, available toboth NetApp employees and partners.

It is designed to simplify the process of performance sizing for NetApp FAS systems running NetApp

Data ONTAP 7G software, Data ONTAP 8.0, 8.1, and 8.2 operating in 7-Mode and clustered DataONTAP 8.1 and 8.2.

1.1 What SPM does

SPM integrates the previous legacy sizers functionality and new features into an intuitive userinterface. In a step-by-step process, it supports multiple workload requirements and producesrecommendations to meet customers performance needs.

Selecting a proper system for the customer is more complicated than just selecting a system that meetscapacity requirements. Performance should be a requirement for any sale and is often morecomplicated to plan for than capacity.

Sizing is the process of obtaining or validating one or more system configurations that can provide thecapacity and performance resources necessary to meet customer requirements. Validation using andreduces the time required to produce recommendations.

SPM versus educated guesses improves sales and customer confidence in the suggested systemconfiguration

The System Performance Modelertool is as shown:

The following options are displayed in the SPM window:

Customer:Displays the customers name as entered in the New Sizing wizard


6/50


Sizing Title:Displays the sizing title as entered in the New Sizing wizard

Workloads:Lists all the workloads added during the sizing workflow

New Sizing:Initiates the workflow for a new sizing exercise

Search:Finds previous sizings based on multiple search criteria

View:Opens previous sizing requests located in history or saved configurations. Sizing templates

are also available from this menu

Help:Shows where additional information can be found, as well as a way to provide feedback to

the SPM team

Toggle:Allows toggling between workflows

Save For Later:Saves the workload and options for later use. The saved date can be retrieved

from the Saved Inputs option from the Viewmenu

Perform Sizing:Allows the user to actually perform the sizing. In the case of the Forward Sizing

workflow, it opens the hardware pre-filter window. In the case of the Reverse Sizing workflow, it

submits the sizing to CSI

1.2 Features in SPM

SPM provides the ability to size systems using a single unified process that supports the following

features and more:

Forward and reverse sizing inputs and recommendations

Data ONTAP 7-Mode or clustered Data ONTAP systems

Multiple common applications

Heterogeneous workloads

Perfstat file input from existing systems

Up-to-date platform and storage performance characterizations

Saving and rehydration

Prior to SPM, standalone application-specific sizers were used to size each application to be

deployed on the system.

SPM is designed to be more intuitive than the previous sizers, and it supports multiple workloads withina single sizing by combining the various independent workload sizers into modules within the workflow.

The following application modules are supported by SPM:

Virtual desktop infrastructure (VDI)

Microsoft Exchange Server (2007 and 2010/2013)

SMB 1.0 and 2.x/3.0 Common Internet File System (CIFS) protocol home directories

Database applications

Microsoft SQL Server

Custom applications


7/50


SPM quick start2

Use the following steps to start working quickly with SPM:

Access SPM using your web browser:https://spm.netapp.com1.

Log into the SPM site by entering your NetApp credentials; partners can use the credentials used2.

for the NetApp Support site.Click New Sizing to create a new sizing request for any of the supported controllers and3.

applications.

Forward Sizing provides a suggested configuration based on a workload.

Reverse Sizing provides the estimated performance for a specific configuration.

Click View > History to review your previous sizings and rehydrate them.4.

Click View > User Templates and System Templates to use predefined templates to guide your5.

sizing efforts.

Click Help > Feedback to provide feedback to the performance sizing team.6.

2.1 Use cases

Depending on the sizing use case, one of the following can help you get started quickly.

New system deployment2.1.1

If you are attempting to size a new storage environment, choose the SPM Forward Sizing workflow.Using this workflow requires some knowledge of the customers workloads and applications.

Completing the Forward Sizing workflow provides recommendations for the number of nodes andnumber of disks, as well as estimated utilizations of the recommended system.

For more information about how to complete a forward sizing, seePerforming a new forward sizing

What if2.1.2

Often a customer would like to know what would happen if additional workloads were applied orhardware changes were made to an existing storage system. The SPM Reverse Sizing workflow usingthe estimated system utilization and latency can be very helpful in this situation.

SPM supports perfstat import, real data from a customer environment can be used in the workflow.After the desired system configuration and workload settings are provided, SPM can provide theestimated system utilization and latencies that should be expected after making the potential changes.

For more information about using the Reverse Sizing workflow, seePerforming a new reverse sizing

Consolidation2.1.3

As systems become more powerful, consolidating a few systems into a single system can be ideal. TheForward Sizing workflow can provide recommendations for consolidation into a new system; if a system

is already deployed, Reverse Sizing workflow solving for system utilization and latency might be moreuseful. If the older systems being considered for consolidation are NetApp storage systems, a perfstatcan be captured and put into SPM to provide the statistics for the NetApp systems.

If systems other than NetApp systems are being considered for consolidation, the workload moduleswithin SPM can be used to enter additional workload details. Completing either workflow should providean idea of what the performance of the single system could be with multiple workloads applied to it.

For more information about saving the credentials, seePerforming a new forward sizingandPerforming a new reverse sizing

Maximum system performance2.1.4

It is important to have an idea of how much of a workload a system can handle. SPM can determine themaximum system throughput using the Reverse Sizing workflow. In this workflow, it is possible to either

upload a perfstat to supply a controller configuration or specify one manually. After completing theworkflow for the reverse sizing in this mode, SPM provides an estimated maximum throughput for thecontroller configuration and workloads
https://spm.netapp.com/https://spm.netapp.com/https://spm.netapp.com/


8/50


For more information about using the Reverse Sizing workflow, seePerforming a new reverse sizing

2.2 Performing a new forward sizing

As previously mentioned, SPM simplifies the sizing process by offering a step-by-step workflow to entersizing-related information and produce sizing results. This section describes the steps of a ForwardSizing workflow. Reverse Sizing has a similar workflow.

Steps

1. Enter opportunity information.This step allows you to enter information about yourself and the potential sales opportunity, aswell as provide notes for future reference regarding this sizing. Only the customer name isrequired to proceed past this step. Any information entered in this step is reflected in the sizingoutput.

Providing a sizing title in this step can make it easier to search for this sizing later. Theinformation entered in this step can be changed later by selecting Customer Information in theView menu on the main SPM window.

The new sizing window is as shown:

.

2. Select sizing workflow and data entry.

This step allows you to select either a Forward Sizing or a Reverse Sizing workflow. In this stepyou can also select whether to use simple or detailed inputs.

After completing the Forward Sizing workflow and submitting the configuration, SPM providesrecommendations for the required number of disks and controllers and information on how datashould be spread across the controller aggregates.

The Reverse Sizing workflow has additional options depending on the information youreinterested in discovering.

For more information about using the Reverse Sizing workflow, see Perform a New Reverse Sizing


9/50


New sizing workflow and data entrywindow is as shown:

3. Select a workload type

This step allows you to select an application workload from the list of supported application

types. If your workload does not exactly match one of the listed workloads, select CustomApplication.

The workload type can also be loaded from different data sources such as a perfstat, yourprevious inputs, or a template.

If a perfstat is used, the Custom Application workload is selected by default and cannot bechanged. The data extracted from a perfstat is used to populate the parameters in Custom

Application workloads.

Forward sizing workload selectionwindow:


10/50


4. Enter the workload informationThe workload information you enter depends on the application selected. This step can be

repeated for as many workloads as required.For more information about workload information, seeUsing the workload modules

5. Perform sizingAfter you have added all of the workloads, submit your sizing request by clicking PerformSizing.

6. Prefilter hardware configurationAfter selecting Perform Sizing, a new window will pop up, which allows you to select thedesired version and operating mode of Data ONTAP, as well as various controller, disk, andflash specifications.

Note: You can select multiple platforms by highlighting the relevant platforms using the control or shiftkeys while clicking. In clustered Data ONTAP sizings, clusters are assumed to be homogeneous inplatform type and configuration, and the systems must be deployed in HA pairs.

SPM does not currently support heterogeneous clusters or configurations that are not in HA pairs.

Also in the forward sizing window is a check box for Degraded Failover Performance OK on HAtakeover event. When this checkbox is not selected, 50% additional utilization headroom is added tothe controller so that the system is capable of completely handling its own workload and its partnersworkload in case of a failover. This might mean that the size of the recommended solution would bedoubled in size.

Note: Degraded failover performance is additive with system headroom. For example, if degradedfailover performance is not checked and headroom is set to 30%, then only (.5 * .7 = .35) 35% of thestorage controller will be utilized, resulting in much larger controllers being needed.

You should select your disk type and the required flash acceleration options. Flash can significantlyreduce the number of disks required to achieve the desired performance, depending on thecharacteristics of the workload.


11/50


A convenient feature of SPM is the ability to size both with and without flash acceleration. Thisprovides the results in a single report and illustrates the effect of the acceleration modules on thepredicted performance of the system.

When sizing for Flash Pool, SPM will identify the number of SSD drives necessary to achieve theperformance requirements of the workloads created in the subsequent steps. This step does not placeany specific workload on a Flash Pool aggregate. All options that are selected will be modeled.

Forward sizing prefilter hardware configurationwindow is as shown:

At this point, you can either click Calculate Sizing or select the Detailed Inputs checkbox to use nondefault options in your sizing. Whether you decide to use some of the detailed inputs or not, clickCalculate Sizing after you are satisfied with the options you have set.

The link to flash recommender tool is included under Flash Acceleration Options

Detailed inputs2.2.1

Selecting detailed inputs gives you the following options:

Allow disk/shelf type selection per workloadIn this section you can over write the global drive and shelf selection. You can also select a new driveand shelf for each workload.

Disk shelf and drives

In this section, you can select the exact disk shelf and disks that you would like to use.

The detailed disk selectionis as shown:


12/50


Flash

Selecting the Flash Acceleration Options checkbox in the Pre-Filter Hardware Configuration window

enables the Detailed Inputs dialog box.

The Auto_Suggest feature has been newly added to the flash acceleration options. This is the default

option, and when this option is selected, the CSI will determine the optimal number, type, and capacity

of the Flash Cache card and also the optimal number and capacity for Flash Pool, based on the

workload characteristics.

You can manually select the type of Flash Cache card, the number of cards, and the capacity of each

card, if you prefer to not use the automatic suggestion option.

Also, you can manually select the type of SSD disk and the amount of capacity of the Flash Pool card

per controller, if you prefer to not use the automatic suggestion option.

The detailed flash accelerationoptions are as shown:


13/50


Advanced options2.2.2

Advanced configuration options can also be set in this step

Note: Changing these configuration options can affect the sizing results.

System headroom (%): Amount of CPU and other system resources that should be reservedand unused while sizing to allow for future growth.

Increasing the headroom can increase the platform count if the supplied workloads exceed theheadroom threshold, even if the workload can be serviced with fewer systems.

Map to full shelves: Select this option if SPM should produce disk requirements equal to thenumber of disks in a full shelf. The final disk count can be increased if the number of disksrequired for performance, capacity, and spares does not equal full shelves.

Capacity reserve (%):Amount of disk space that should be reserved for future growth. This

can increase the number of disks required to meet capacity requirements.

Spare disks per node:The number of disks that should be added as spares.

Note:SPM automatically calculates the number of parity drives required.

System age:As system age increases, I/O operations can become less optimal, whichultimately increases disk utilization. Adjusting the system age can increase the amount of disksrequired to support the workload. The Empty System setting represents a new storageenvironments age.

Forward sizing advanced configurationoptions are as shown:

7. Review SPM outputAfter SPM completes the sizing, a results summary window appears displaying the sizingoutput. The top portion of the results window shows the various configurations that were sizedand are included in the report. To view the complete sizing report, select View Report.

For more information about SPM sizing, seeUnderstanding SPM sizing output

If there are any issues with the output of SPM, clicking Feedback prepopulates a feedbackmessage with the sizing ID. Any questions or comments submitted through the feedback

mechanism are sent to the NetApp SPM team.

Forward sizing results window is as shown:


14/50


2.3 Importing workload from AutoSupport

The Import Workload allows the user to import workload information for sizings through AutoSupport.

It does not import controller specification or pre-filter configuration AutoSupport records hourly averages for IOPS

It imports throughput and the required capacity values from ASUP. The following fieldsare set to default values:

o IO sizeo IO percentageso Working set size

The AutoSupport window is as shown:


15/50


.

2.4 Importing from custom app workloads

This feature supports the importing of the Custom Application workloads. The Custom Applicationworkload has to be saved in a JSON file format. You can import multiple Custom Application workloads.

The Custom App Workload window is as shown:


16/50


2.5 Performing a new reverse sizing

The Reverse Sizing workflow for SPM is similar to the Forward Sizing workflow. However, it answers

different questions. Forward sizing is primarily focused on new sales; reverse sizing is focused onexisting installations. SPM provides two methods of reverse sizing:

Estimate resource utilizations and latencies, which answers the what if questions

Estimate maximum throughput, which provides the exact opposite of a forward sizinglikefunctionality

Starting with SPM 1.4, the reverse (formerly advanced) sizing workflow is supported for both 7-Modeand clustered Data ONTAP.

When using the Reverse Sizing modes, only a single platform model can be selected.

Also, instead of solving for the number of disks, the aggregate sizes and types are user defined usingthe aggregate attributes feature. There are no additional advanced parameters, such as capacity

reserves of spare disks, because aggregates are user defined and have already been determined.

Note: You can toggle between the forward and Reverse Sizing workflows by clicking the Toggle buttonat the bottom of the SPM window.

The sizing method selectionis as shown:


17/50


This section describes how to complete a reverse sizing for both resource estimation and maximumthroughput calculations.

Steps

1. Enter opportunity information.

After clicking New Sizing, this step is the same as in a forward sizing. This window allows youto enter information about the opportunity, which is then included in the output report and

enables easier searching.

2. Select sizing workflow and data entry

In a reverse sizing, you must first select whether the inputs are to be manually entered orloaded from a perfstat file. Then, a choice for the attribute on which you are going to estimateperformance is needed. The selection depends on the end result that is desired. The workflowfor both options is similar, although the outputs are different.

Resource Utilization and IO Latencies:This option is useful for answering a what ifquestion. For example, if a system is already deployed and a customer wants todetermine what would happen if another workload were deployed on it, using this sizingmethod will determine what the customer should expect for overall system utilizationand latency.

Maximum Throughput:This option is the exact opposite of a forward sizing. SPMprovides an estimated maximum throughput given a system configuration and one ormore application workloads.

A perfstat file can be uploaded during this step.

Selecting reverse sizing workflowis as shown:

3. Select controller configurations.

Unlike with a forward sizing, only a single controller platform model can be selected in areverse sizing. Also, because SPM cannot determine the layout of the workloads, no CPUheadroom or disk count parameters are required. Flash Cache modules can also be included.


18/50


If this is a clustered Data ONTAP configuration, the number of HA pairs needs to be set.

Entering the number of HA pairsin clustered Data ONTAP is as shown:

The FlashCache options section enables you to select no Flash Cache or specify the exact type,number, and size of the cards.

The flash cache optionsin reverse sizing are as shown:

In this step, aggregate configurations must be defined. For each aggregate that is part of the system

being modeled, add an aggregate and the number of disks in the Aggregate Attributes window usingthe New Aggregate button. SPM assumes that the RAID type is NetApp RAID-DP

technology and

uses the default RAID group size (16). For guidance on RAID group and disk spare configurations,refer to theStorage Subsystem Technical FAQ.

Adding an aggregatein reverse sizing is as shown:
https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=9866https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=9866https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=9866https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=9866


19/50


4. Select a workload type

In this step, you can select an application workload from the list of supported application types.If your workload doesnt exactly match one of the listed workloads, select Custom Application. Ifyou are solving for maximum throughput, the only option available is the Custom Applicationworkload module.

Choosing a workload typein reverse sizing is as shown:


20/50


5. Enter workload information.

The workload information you enter depends on the application selected. This step can berepeated for as many workloads as needed.

For more information about using workload, seeUsing the workload modules

6. Perform sizing or save for later.

Now you can perform the sizing or save and continue later, just as with the Forward Sizingworkflow. When you're ready to submit, click Perform Sizing on the bottom of the main window.

7. Review SPM output.

The output of SPM at this point depends on the option selected for reverse sizing. Followingare the examples of types of output:

Estimating system utilizations and latency outputin reverse sizing is as shown:


21/50


Estimating maximum throughput outputin reverse sizing as shown:

The results of the reverse sizing are also captured in the report available from the results window.

For more information about the report, seeUnderstanding SPM sizing output


22/50


Sizing with flash cache and flash pool acceleration3

Starting with SPM 1.4, sizing with flash acceleration options sections have been updated. AnAuto_Suggest option has been added for both Flash Cache and Flash Pool options, in addition to theoption to manually specify the type and quantity.

3.1 Changes to user interface

Flash acceleration options

When selecting the Pre-Filter Hardware Configuration option in a Forward Sizing workflow, the flashaccelerations options are presented as checkboxes to enable or disable SPM from analyzing each one.

Both Flash Cache and Flash Pool default to Auto_Suggest, which allows CSI to determine the optimalnumber, type, and capacity of Flash Cache and also the optimal number and capacity for Flash Pool,based on the workload characteristics.

Flash Acceleration optionsare as shown:

When the Detailed Inputs checkbox is selected, the following more detailed options are allowed to beselected.

Flash acceleration option - Auto_Suggest

The flash acceleration options section of the SPM wizard now includes the Auto_Suggest option, inaddition to the existing No and Manual options.

The Auto_Suggest option is enabled by default. When this option is enabled, CSI will determine theoptimal number, type, and capacity of Flash Cache and also the optimal number and capacity for FlashPool, based on the workload characteristics.

CSI will generate two outputs per platform/drive combination selected: one output with only FlashCache and the other with only Flash Pool, based on the workload characteristics.

Auto_Suggestin Flash acceleration options as shown:

Flash acceleration option - No

If you do not want flash options in the output, do not select the Flash Cache and Flash Poolcheckboxes. CSI will generate only one output per platform/drive combination selected, without FlashCache and Flash Pool in the suggested configuration.

Flash acceleration option - Manual

The Manual mode is available for the user to specify, if so desired, the number, type, and capacity ofFlash Cache and/or the number and the type of the SSD drives for Flash Pool to be used for the

workloads.


23/50


When both the Flash Cache and Flash Pool manual modes are selected and inputs provided, CSI willgenerate two outputs per platform/drive combination selected: one output with only Flash Cache andthe other output with only Flash Pool, based on the workload characteristics.

Manual option in Flash Acceleration is as shown:

3.2 Creation of aggregates enabled by flash pool

SPM 1.4 supports the creation of aggregates enabled by Flash Pool during reverse sizing in both DataONTAP 7-Mode and clustered Data ONTAP. A new field, Aggr Type, has been added to enable theselection of the aggregate type to be created. The Aggr Type can be selected as either Normal orFlashPool Enabled.

When the Aggr Type is selected as FlashPool Enabled, two new fields will display in which the user canspecify the SSD drive type and SSD data drives.

Aggregate enabled by Flash Pool is as shown:

3.3 Flash output changes

In older versions of SPM, when both Flash Cache and Flash Pool were enabled, CSI used to combineboth of them and generate one output per platform/drive combination selected. With the addition of theAuto_Suggest option, the CSI outputs have also changed.


24/50


When both the Flash Cache and Flash Pool options are selected, either in Auto_Suggest or Manualmode, CSI will generate two outputs per platform/drive combination selected: one output with onlyFlash Cache and the other with only Flash Pool, based on the workload characteristics.


25/50


Importing workload information4

Workload information can be gathered and imported a variety of ways. SPM supports importingcontroller and workload information from perfstat files as well as workload information from previous orsaved sizings.

Importing Workloadcapabilities is as shown:

4.1 Perfstat

Perfstat is a NetApp tool used to capture performance and configuration information from an existinginstallation. SPM supports uploading perfstats to automatically fill in the controller and workloadinformation necessary for sizing. After a perfstat is uploaded, its possible to modify the controller andworkload to model changes to an existing system. SPM allows you to submit perfstat files in two ways:online and offline.

Perfstat parseroptions are as shown:

Online perfstat parsing

For online perfstat parsing, NetApp internal users can provide a valid internal path to a perfstat file intheir home directory. With this method, the perfstat file is fetched by SPM without the need to upload alarge file.

For all users, a perfstat file can be uploaded directly into SPM. If the perfstat file is large, consider usingthe offline perfstat parser.

Online perfstat parser is as shown:


26/50


Offline perfstat parsing

If a perfstat file is stored locally, the offline parser can be used. The offline perfstat parser uses a utilitybased on Java that parses through the perfstat file and generates an intermediate file that SPMunderstands. The parsed perfstat intermediate file is much smaller and therefore uploads more quicklycompared to the perfstat file. This method requires that the Java Runtime Environment be installed onthe local machine for the utility to work properly.

After the offline parser is selected and allowed to run, an additional HTML page loads, providing theinterface to the offline parser. Use the following steps to parse a perfstat file:

Steps

1. Select a perfstat file to parse.

Perfstat file selectiondialog box is as shown:

After the perfstat file is parsed, a list of controllers in the perfstat file is made available.

2. Select the desired controller configurations and then select the workload characteristics.


27/50


Perfstat parser system configurationdialog box is as shown:

3. Select the desired iteration and option (Min, Max, or Average IOPS and CPU).

Perfstat parser workload characteristicsdialog box is as shown:

After the controllers and workloads are selected, the parser prompts for a location in which to save anintermediate file (.spm file).

4. Save the file.

5. Close the parsing window after the file is saved. SPM then displays the Import workloads fromPerfstat page. Use the Browse button to browse for the intermediate file (the .spm filegenerated in step 3).

Offline perfstat parser intermediate file uploadis as shown:


28/50


The information in the perfstat file to be used for the sizing should now be visible on the main SPMwindow as a controller configuration and a workload configuration.


29/50


Using the workload modules5

The following sections describe how to use each of the application-specific modules. Application-specific variables are defined in each section; how the variables affect the sizing output is alsodescribed.

Some elements are common among all of the sizing modules, such as layout and NetApp SnapMirrorfunctionality. These elements are covered in the Additional Sizing Options section.

5.1 Virtual desktop infrastructure module

The virtual desktop infrastructure (VDI) module provides an easy-to-use interface to size for multipledifferent VDI environments. Most of the inputs require that the sizing module be available from thecustomers proposed or existing environment.

The protocol type is the storage protocol that will be used to host the virtual machines (VMs). Eachprotocol has different performance characteristics. The module also supports VMware, Citrix, andMicrosoft hypervisors as well as various cloning methods.

The following list describes the fields of the VDI interface.

The basic window will have the mandatory fields, and the details will all be set todefault values; however, the user can expand the detailed section and set personalvalues.

Free aggregate space and free snap reserve define the amount of free space that mustbe kept in the aggregate and the amount that should be reserved for NetAppSnapshot copies.

The number of input/output operations per second (IOPS) is the amount of I/O eachuser is estimated to produce.

The C drive size (in GB) is the size of the main VM operating system drive.

VM memory size refers to the amount of memory per VM and is used to factor in thevswap storage requirements.

Unique data per VM is the estimated space unique to each VM. Because of cloning

and deduplication technologies, VMs might not require much additional space. Thishelps define additional storage requirements for the life of the VM.

Note: Disk capacity requirements can vary significantly depending on the cloning and Snapshottechnologies employed. Make sure to understand these differences when sizing for VDI environments.

The read and write workload estimates are the percentage of read and write I/Oexpected from the VMs.

Working set size defines the percentage of the total data that is considered active andcan vary depending on the customer environment.

Read and write I/O size defines the I/O size for the workload.

Random read latency defines the maximum allowed latency for reads.

VDI workload inputsare as shown:


30/50


VDI detailed inputsare as shown:


31/50


Sizing output can vary significantly based on differences found in vendors cloning technologies, soNetApp recommends reviewingTR-3949: NetApp and VMware View Performance Report.

Detailed instructions on the deployment characteristics of VDI technologies are beyond the scope ofthis document; therefore, NetApp recommends engaging with a consulting systems engineer (CSE) inyour area when sizing any VDI opportunity.

5.2 Microsoft exchange 2007 moduleThe information necessary to fill out the workload parameters needed to complete this module can beacquired by filling out theExchange 2007 Mailbox Server Role Storage Requirements Calculator.

Because providing detailed instructions on the technical and deployment characteristics of MicrosoftExchange is beyond the scope of this document, NetApp recommends engaging with a CSE in yourarea when sizing any Exchange opportunity.

5.3 Microsoft exchange 2010/2013 calculator import module

In addition to the manual entry Microsoft Exchange application module, an additional module has beenincluded in SPM that supports the upload of the Microsoft Exchange 2010/2013 Mailbox Server RoleRequirements Calculator. This application module requires theExchange 2010 Mailbox Server Role

Requirements CalculatororExchange 2013 Server Role Requirements Calculatorspreadsheet.

When sizing for Exchange using SPM, review the recommendations and best practices inTR-4166i:NetApp System Performance Modeler and Microsoft Exchange Server 2010.

To complete a sizing, do as follows:

Steps

1. Enter the values in the exchange mailbox server role requirements calculator sheet.

In the Inputs sheet of the calculator, perform the following actions:

Under Backup Configuration, select Yes for Database and Log IsolationConfigured. Otherwise, the database and log will be placed on the same LUN,which is against NetApp best practices and will result in a configuration that will

not work with SnapManager for Exchange.

If the database size is less than the NetApp best practice of 2TB minimum, it willadversely affect the performance of the system, because each database performsmaintenance. Make sure that you set the Maximum Database Size Configurationvalue to Custom. Set the Maximum Database Size (GB) to a value greater than2TB until the actual database size is close to 2048GB. This value can be viewedin the LUN Requirements (in Exchange 2010 calculator) and VolumeRequirements (in Exchange 2013 calculator) and in column E under DB size +overhead.

Under Backup Configuration, select the VSS Hardware Provider for BackupMethodology.

Under Exchange Data Configuration, select Yes for DedicatedMaintenance/Restore Volume.

Under Exchange I/O Configuration, specify the additional I/O or serverrequirements.

Under Tier-1 User Mailbox Configuration, select Yes for Desktop Search EnginesEnabled (for Online Mode Clients).

Under User Mailbox Configuration, selecting Yes for Desktop Search EnginesEnabled will affect the IOPS accordingly.

Using the online retention settings affects the capacity calculations.

2. Upload the completed copy of the Mailbox calculator by clicking the Browse button in the basic

inputs section.

Exchange 2010/2013spreadsheet upload component is as shown:
https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=36433https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=36433https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=36433http://gallery.technet.microsoft.com/Exchange-2007-Mailbox-ca00a684http://gallery.technet.microsoft.com/Exchange-2007-Mailbox-ca00a684http://gallery.technet.microsoft.com/Exchange-2007-Mailbox-ca00a684http://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-http://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-http://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-http://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780https://fieldportal.netapp.com/?oparams=127078https://fieldportal.netapp.com/?oparams=127078https://fieldportal.netapp.com/?oparams=127078https://fieldportal.netapp.com/?oparams=127078https://fieldportal.netapp.com/?oparams=127078https://fieldportal.netapp.com/?oparams=127078http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780http://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-http://gallery.technet.microsoft.com/office/Exchange-2010-Mailbox-Server-Role-http://gallery.technet.microsoft.com/Exchange-2007-Mailbox-ca00a684https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=36433


32/50


3. After the application module workflow is completed, two workloads are generated within SPM, aprimary site and a secondary site. Modify the controller constraints and use the checkboxesnext to the generated workload to model the primary and secondary workloads independently.

5.4 SMB 1.0 CIFS home directories module

Various factors must be considered for each home directory deployment. The key considerations forarchitecting and sizing a CIFS home directory solution include the number of users, the number ofconcurrent users, the space requirement for each user, and the network load. Additional factors, suchas virus scanning of the home directories, can also affect sizing recommendations.

SPM supports these various considerations in the CIFS home directory workload module. The initialworkload parameters include:

Workload Description:An appropriate description of the workload for easyreference.

Number of Users: The total number of users accessing the data.

User Type:Select from light, low, medium, or heavy; based on this, the otherdependent values will be set to default optimal values.

Home Directory Size (GB):The amount of space required for each user.

Home directory specifications are as shown:

The following list describes various user parameters. The number of users along with the size of thehome directory defines the capacity requirements; the number of users along with type of user and

concurrency defines the performance requirements. The user type is based on the data transfer raterequirement per user.

Light user = ~3kB/s


33/50


Low user = ~5kB/s

Medium user = ~10kB/s

Heavy user = ~20kB/s

Additional parameters include:

Concurrency (%):The percentage of active users at any point in time.

Throughput type:Choose between MB/s and IOPS, depending on what thebasis of the sizing should be. The default value is MB.

Random read latency (ms):If latency other than 20ms is required for thisdeployment, enter the value here.

Sizing options:This option allows you to further customize the configurationbased on the deployment type designated as one of the following:

Fresh installation

Migration from non NetApp storage

NetApp upgrade

User profilesoptions are as shown:

The CIFS home directory sizing workload module was implemented based onTR-3564i: Sizing ofCIFS-Based Home Directories.Although this document is no longer current, refer to it for additionalreference material.

5.5 SMB 2.x/3.0 CIFS home directories module

If clustered Data ONTAP 8.2.x or later is selected, sizing for SMB 2.x and 3.0 is supported. Various

factors must be considered for each home directory deployment. The key considerations forarchitecting and sizing a CIFS home directory solution include the number of users, the number ofconcurrent users, the space requirement for each user, and the network load.

Additional factors, such as virus scanning of the home directories, can also affect the sizingrecommendations.

SPM supports these various considerations in the CIFS home directory workload module. The initialworkload parameters include:

Workload Description:An appropriate description of the workload for easyreference.

Random Read latency (ms):Input the desired latency as specified inmilliseconds. This defaults to 20ms, which is considered a reasonable value.

User Type:Sets how much usage each user will add. Select from light (3kB/s),medium (10kB/s), or heavy (20kB/s); based on this, other dependent values willbe set.

Number of User:The total number of users accessing the data.

Concurrency %:This specifies what percentage of the users would actually beusing the system at one time.

Home Directory Size (GB):The amount of space required for each user.

CIFS 2.x/3.0 home directoryspecifications are as shown:
https://fieldportal.netapp.com/ci_getfile.asp?method=1&uid=5156&docid=11218https://fieldportal.netapp.com/ci_getfile.asp?method=1&uid=5156&docid=11218https://fieldportal.netapp.com/ci_getfile.asp?method=1&uid=5156&docid=11218https://fieldportal.netapp.com/ci_getfile.asp?method=1&uid=5156&docid=11218https://fieldportal.netapp.com/ci_getfile.asp?method=1&uid=5156&docid=11218https://fieldportal.netapp.com/ci_getfile.asp?method=1&uid=5156&docid=11218


34/50


5.6 Database applications module

The database workload module can be used to size most common database applications. SPMconveniently provides a way to upload statistics files from existing database installations that can helpfill in the various workload parameters in this module. SPM supports Oracle statspack and automaticworkload repository (AWR) files as well as statspack4SQL. Select the Detailed Inputs checkbox andthen click Browse to select the relevant statistics file. This will populate most of the values in this dialogbox.

Database statistics file importdetails is as shown:

If a statistics file is not used, the workload characteristics can be entered manually. The performanceinputs fields are for specifying the basic characteristics of the database workload, such as throughput,operating-mix percentages, throughput growth, and maximum acceptable latency.

Performance inputsfields options are as shown:


35/50


App Specification Inputs fields allow you to select the database type to use for this sizing request, theprotocol to use, and the project life, which aids in the definition of growth requirements.

App specification inputsfields are as shown:

The file system inputs section of the database sizer helps to define the capacity requirements for thedatabase application. The working set size parameter defines what percentage of the capacity is activeat any point in time.

File system inputsfields are as shown:

The performance of the storage system also depends on the block size used by the application. Thedefault is 8KB, but other sizes can be specified, if necessary.


36/50


DB-specific inputsfield are as shown:

Because detailed instruction on the technical and deployment characteristics of the various databasessupported by SPM is beyond the scope of this document, NetApp recommends engaging with a CSE inyour area when sizing any database application.

5.7 Custom application module

For workloads that dont fit any of the built-in application modules or for workloads that need moregranular control, use the custom application module.

Although the custom application module supports all protocols, only one protocol can be selected perworkload. If you must consider additional protocols, simply duplicate and modify the workload.Throughput can be defined as IOPS or MB/s. Select the appropriate throughput type, because it affects

how the throughput value is interpreted.

The required capacity field defines the size of the entire dataset and is used for storage capacityplanning if the number of disks is not determined by performance requirements. Capacity growth canbe considered when selecting capacity reserve in the Forward Sizing workflow.

Basic inputsin custom application module are as shown:

The rest of the fields covered are defaulted, but can be modified by clicking the Detailed Inputs checkbox.

When specifying a random read latency, make sure that it is reasonable and also meets therequirements of your application. Enter the desired latency in milliseconds. This defaults to 20ms, whichis considered a reasonable value.

Workloads associated with aggregates that only have hard disks (HDDs) have a floor of a 8ms latency.Workloads associated with aggregates, which have SSDs, have a floor of a 3ms latency. Latencies setbelow these values might return an error.

Random Read Latencyin custom application module is as shown:

The I/O percent section defines the read-write breakdown of the workload. The options at the top of theI/O percent parameters are presets that quickly adjust the percentages. If you know the breakdown ofyour workload in greater detail, the percentages are adjustable. This defaults to 25% of each of the fourcategories.

I/O percentworkload parameters are as follows:


37/50


The working set size, which is generally applicable to workloads with random I/O, defines the size ofthe active portion of data. This value affects how much data can be cached, which affects how much ofthe workload is forced to disk.

The smaller the working set, the greater the chance that data is kept in the cache. The working set sizeis not often known for many applications, but its typically a smaller percentage of the total data.

Application working set size recommendations

Guidelines to determine working set sizes based on workload type.

Application Working Set as Percentage of File Set or Storage

Home directories 3%10% of total file set

Databases (OLTP) 5%20% of database size

Microsoft Exchange 100% of database size (Exchange 2003);

~80% of database size (Exchange 2007 and Exchange 2010)

Other e-mail applications ~20% of storage space

Working set sizeparameter in custom application module is as shown:

Changing the size of the I/Os in the workload can affect the number of IOPS that the system willachieve. However, total data throughput in MB/s might be greater. Set these values to be as close aspossible to the customer workload characteristics.

I/O size parameters in custom application module are as shown:

If Flash Pool is used for this application workload, the random overwrite percent selection is madeavailable. Random overwrite percent determines the impact that the random overwrite caching in SSDwill have for the workload and system performance.

Random overwrite percent selection is as shown:


38/50


After the application-specific portions of the workload are complete, there are additional points toconsider that are common to all applications, such as layout hints, aggregate types, and SnapMirrorfunctionality.

For more information, seeAdditional sizing options


39/50


Additional sizing options6

This section describes additional sizing options that exist for all of the workload modules.

6.1 Layout options

A key strength delivered by SPM is support for extensive customization of storage layout andconfiguration options, detailed in the sizing output reports. This functionality is particularly powerful inclustered Data ONTAP opportunities, and we encourage exploration of the various layout configurationparameters.

The layout hint options within each of the application workload modules define how the workload shouldbe spread across the nodes in the system. Placing a workload on a shared aggregate means that morethan one workload can be placed on the same aggregate, if necessary.

Workloads can be split between the nodes on different aggregates, or they can be contained in a singleaggregate on a single node. Splitting the workload across multiple aggregates means that the workloadcan be split across the nodes in the system.

Selecting this box means that all the nodes in the system will get a portion of the storage workload. This

applies to both Data ONTAP 7-Mode and clustered Data ONTAP systems.

If the system configuration includes Flash Pool, the layout hints section designates whether theworkload should be placed on a Flash Pool aggregate.

Layout hintsare as shown:

When defining workloads to be placed on a clustered Data ONTAP system, additional options areavailable. The flexibility of clustered Data ONTAP allows client access to be split across nodesregardless of whether the data is stored on one node or on many nodes.

Additional clustered Data ONTAPlayout hints are as shown:

The following combinations are possible depending on how the layout options are set for the workload:

Remain on a single aggregate (do not split)o With direct access only to a single node (A)o Distributed client access across all nodes, sent over the cluster interconnect to

the node responsible for the aggregate (B).


40/50


Allowed to exist on multiple aggregates (able to be split)o With direct access only (C)

o With fully distributed access across the cluster interconnect (D)

All four layouts are possible for clustered Data ONTAP system sizings; only A and C are applicable toData ONTAP 7-Mode systems.

Workload layout combinationsare as shown:

6.2 SnapMirror options

7-Mode

For each workload in a Data ONTAP 7-Mode sizing, during reverse sizing, there is an option to includeSnapMirror parameters related to the workload.

SnapMirror featuresare as shown:

Clustered ONTAP mode

Forward sizing

For each workload in a clustered Data ONTAP sizing, during forward sizing, there is an option toinclude SnapMirror parameters related to the workload.



41/50


Reverse sizing

For each workload in a clustered Data ONTAP sizing, during reverse sizing, there is an option toinclude SnapMirror parameters related to the workload.


6.3 System generated intermediate workloads

Most of the workload modules ask for characteristics a customer should be able to provide. SPMtranslates these user inputs into workload characteristics that it can use for sizing. These system-generated workloads are not directly editable, but are indirectly changed by modifying the workloadinputs.

The system-generated workload characteristics can be viewed after a workload is added to the currentsizing. Clicking Edit under Options to the right of a workload brings up the user-entered workloadparameters, as well as the system-generated values and intermediate values. For example, completingthe Exchange Workload entry produces two system-generated workloads.

Example:

SnapMirror system-generated workloadsare as shown:


42/50


Intermediate calculations of SPM are as shown:


43/50


Understanding SPM sizing output7

This section explains how to interpret the output report produced by SPM. Most of the elements are thesame between Data ONTAP 7-Mode and clustered Data ONTAP.

Specific elements are described in each section. The examples shown are screenshots of the output

produced by using the default workload options in the custom application sizer module.

7.1 Suggested configuration and layout

The following is sample report that shows six different configurations, including Flash Cache, FlashPool, and without any flash. Notice that the number of nodes varies based on the platform and theamount and type of flash used.

Suggested configuration and layoutis as shown:

7.2 Layout recommendations

Depending on the mode selected (7-Mode or clustered Data ONTAP), this section describes howworkloads are spread across the controllers or nodes in a cluster. The distribution across the controllersor nodes in a cluster is ultimately dictated by the options selected in the layout hints section for eachworkload.

For clustered Data ONTAP, the table in this section also describes whether the traffic is direct orindirect. The following examples are of the type of data found in the report.

For more information about how to affect the layout, seeLayout options

Example:

Controller layout (7-Mode)is as shown:

Node layout (clustered Data ONTAP, direct only)is as shown:

Node layout (clustered Data ONTAP distributed across cluster)is as shown:


44/50


7.3 Controller/Node perspective system utilization

This section describes the estimated utilization at the individual controller level within the overallsystem. The utilization reported by SPM is not the same as the utilization of any specific componentwithin the system. For example, 60% system utilization does not correspond to 60% CPU or 60%overall disk utilization. The 60% utilization means the sized throughput is 60% of the total systemthroughput given the current workload characteristics.

For each controller, there is a list of workloads applied to that system. A sample table from the report inwhich system utilization under workload details shows how much a specific workload affects the node.

System utilization under controller details is the overall system utilization, which also includes some ofthe system overheads expected for this configuration.

Data ONTAP 7-Mode

Controllerperspective system usage (7-Mode) is as shown:

Controller usage graph(7-Mode) is as shown:

Clustered Data ONTAP

The following illustration is a sample from the report that shows how each node is affected by theworkload distributions. Direct streams appear once in the table on the node that is receiving the stream.

Indirect streams are reflected on two nodes:

The node processing the client traffic

The node containing the aggregate and actually serving the data

Each workload shows how much system utilization it is contributing to the node, and the overall systemutilization, under node details, reflects the sum of all the workload utilizations along with additionaloverhead.

The node receiving client traffic and forwarding indirectly will have a lower utilization than the nodereceiving the indirect traffic and accessing the storage.

Multiple workloads are adjusted depending on the layout hints.

Node-perspective system usage(clustered Data ONTAP, direct only) is as shown:


45/50


Node-perspective system usage (clustered Data ONTAP, distributed across cluster) is as shown:

7.4 Drive calculations and flash pool

This section describes how SPM determines the number of drives required to support the workload.The following report shows whether the number of drives is determined based on the performancerequirements or on the capacity requirements.

It also shows the number of drives required for RAID and other requirements. Choosing different drivetypes, capacities, and Flash Cache can affect these numbers.

Drive calculationsare as shown:

If Flash Pool is used in the sizing, this table changes to show the disks required for both the SSD andHDD portions of the Flash Pool aggregate. The expected impact of read caching of Flash Pool is shown

below.Flash Pool drive calculationsare as shown:

The shelf details section elaborates on the number of shelves, drive types, and number of drivesneeded for the configuration.

7.5 Adjustments for drives and other outputs

A report that shows the total number of drives for the system based on additional requirements, such asthe number of spares requested or if the system should map to full shelves.

Flash Pool impactsare as shown:


46/50


Drive calculation adjustmentsare as shown:

Other outputs can also be produced if they are relevant to the sizing request. Some examples includeinformation about the size and number of Flash Cache modules or the disk-OPS-to-host-OPS ratio.

Additional information outputsare as shown:

7.6 Node increment details

The node increment details about sizing are provided for better understanding and possible

remediation.

The node increment detail is as shown:

7.7 Inputs section

The inputs section of the report includes all of the controller and workload inputs used to generate thesizing report.

7.8 Failed configurations section

Not all configurations are valid for sizing with SPM. If multiple controller configurations are specified for

a forward sizing, its possible that some of them are valid, and others are invalid. The failedconfigurations section of the report provides a table of sizing configurations that failed to complete andthe reason for the failure.

Example:

Failed sizing is as shown:


47/50


7.9 Reverse sizing report

If the Reverse Sizing workflow was used, the report contains a table with the requested sizinginformation. When sizing for system utilization and latency, SPM creates a table

Reverse system utilizationsizing report is as shown:

When sizing for maximum throughput, SPM creates a table. In addition to maximum throughput, SPMalso lists the reason for the bottleneck that is limiting the performance of the configured system.

Reverse maximum throughput sizing reportis as shown:


48/50


Additional resources8

Additional information can be found in the SPM help menu, as well as in theSPM FAQ.For moreinformation, contact thesizing teamor visit theSizers Communitypage.
https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=41678https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=41678https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=41678mailto:[email protected]:[email protected]:[email protected]://communities.netapp.com/community/netapp_partners_network/netapp_tools/sizershttps://communities.netapp.com/community/netapp_partners_network/netapp_tools/sizershttps://communities.netapp.com/community/netapp_partners_network/netapp_tools/sizershttps://communities.netapp.com/community/netapp_partners_network/netapp_tools/sizersmailto:[email protected]://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=41678


49/50


Version history9

Version Date Document Version History

Version 0.1 March 2012 Original version

Version 1.0 March 2012 Updated for SPM 1.0 general availability

Version 1.1 September 2012 Updated for SPM 1.1

Version 1.2 December 2012 Minor updates for SPM 1.2.1, specifically the Microsoft ExchangeCalculator capability

Version 1.3 December 2013 Updated for SPM 1.4

Version 1.4 January 2014 Updated for SPM 1.4.1

Version 1.5 May 2014 Updated for SPM 1.5


50/50

SPM User Guide

Documents