PowerStore+Design+PowerSizer+ +Participant+Guide (PDF) +4
PowerStore+Design+PowerSizer+ +Participant+Guide (PDF) +4
POWERSIZER
PARTICIPANT GUIDE
PARTICIPANT GUIDE
PowerStore Design PowerSizer
Workload Characterization 12
Characterizing I/O Workloads 12
Typical I/O Characteristics 12
Sizing Considerations 14
Knowledge Check 3 14
Workload Handling 27
Sizer Workload Handling: Overview 27
Workload Handling (PowerStore T) 27
Workload Handling (PowerStore X) 28
Knowledge Check 7 29
Customizing Workloads 37
Customizing Workloads: Overview 37
Split Workloads in Sizer Path 37
Splitting Workloads 38
Editing and Adding Workloads 39
Moving Workloads 40
Cloning Workloads 41
Knowledge Check 9 42
Project Management 43
Sizing Projects 43
My Projects Screen 43
Scenario Options 45
Scenario Options: CONNECTIVITY Tab 46
Scenario Options: POWER Tab 47
Appendix 69
Introduction to PowerStore
Different PowerStore models have different CPU speeds and core counts,
which help to achieve different I/O performance potentials. In general, the
IOPS capability of the PowerStore models scales linearly from PowerStore
500 onwards.
Designing solutions with these models involves sizing the solutions for
customers to arrive at a configuration that supports the wanted workloads
at the required performance level.
Knowledge Check 1
TAs have an online planning tool called PowerSizer (also called Sizer) to
work out the right PowerStore, PowerMax, PowerScale, PowerVault, and
APEX configurations for optimal performance. This course focuses on
PowerStore solutions.
PowerSizer dashboard
Overview of PowerSizer
PowerSizer Dashboard
PowerSizer dashboard
PowerSizer Output
PowerSizer output
Knowledge Check 2
PowerSizer dashboard
Workload Characterization
Think:
What is available in the network, and how much work does the
network and storage have to do?
Block
IOPS
MiB/s
File
VMs
Sizing Considerations
PowerStore T
PowerStore X
Knowledge Check 3
b. 50-60%
c. 40-50%
d. 70-80%
4: Performance: User input for the workload (in K IOPS) or throughput (in
MiB/s) that is based on the appliance workloads in the cluster
Workload Templates
Knowledge Check 4
1. If you do not know the block size of a workload, what would be a good
size to use?
Select the correct option and then select Submit.
a. 8K
b. 32K
c. 16K
d. 64K
1: Protocol: Options are Network File System (NFS) and Server Message
Block (SMB).
MiB/s is entered but not File PowerSizer adds the MiB/s value
Operations to block MiB/s for cluster and
appliance summary details. The
block MiB/s does not contribute to
the summary IOPS because no
I/O size is defined.
Both OP/s and MiB/s are specified Some level of the OP/s might
in the characterized workload contribute to the MiB/s and vice
versa; that is, there are file
operations that aren’t reads or
writes. The workload can be
specified as a single workload or
two workloads; both inputs impact
the performance and capacity
utilization differently.
Knowledge Check 5
PowerSizer output
a. IOPS
b. File Operations/Sec
c. Response Time
d. Latency
1: Total VMs: Virtual machine count for the current group characterization
Default value: 0
Default value: 0
Default value: 0
4: IOPS Per VM: Expected I/O per VM (in K IOPS), using the
characteristics in the block storage definition area
Default value: 0
Default value: 0
Default value: 0
PowerStore X Considerations
Knowledge Check 6
1
PowerStore 7000X with 1 VCPU/VM and Medium 4:1 CPU Util value will
allow a maximum of 160 VMs with up to 4 GiB of memory.
Workload Handling
How does Sizer handle workloads at the block and file levels?
2
Performance requirements associated with workloads are specified as
follows:
• Block workload on PowerStore T: IOPS, MiB/s, data reduction ratio,
effective capacity
• File workload on PowerStore T: File Operations/Sec and/or
Operations/Sec and/or MiB/s
PowerStore T Solutions
Block Workload
File Workload
PowerStore X Solutions
VM Workload
Block Workload
Knowledge Check 7
This topic looks at the recommended use of the Quick Size section of
PowerSizer and the Sizer path process for sizing.
The Quick Size section allows you to choose a product family for sizing
purposes.
The typical use cases for the Quick Size option include:
Workloads page
Select a solution from the displayed options and then select SAVE to save
that sizing scenario.
PowerSizer output
PowerSizer output
Knowledge Check 8
Customizing Workloads
PowerSizer output
PowerSizer output
Important:
Splitting workloads eases the entry of high workload
counts by consolidating the input characteristics in
Sizer and letting PowerSizer determine the workload
distribution.
In case of split workloads, Sizer balances the
performance saturation across appliances. However,
one appliance in the solution may end up with lower
saturation than other appliances.
The distribution of performance will be influenced by
the specified constraints.
Splitting Workloads
Apart from splitting workloads, PowerSizer Editor also allows the addition
and modification of workloads, as required, to optimize the capacity
utilization, system saturation, storage performance saturation, and latency
at the cluster level for a proposed solution.
PowerSizer Editor
Moving Workloads
PowerSizer Editor
Cloning Workloads
PowerSizer Editor
Knowledge Check 9
a.
Move icon
c.
Copy icon
e.
Delete icon
Project Management
Sizing Projects
PowerSizer dashboard
My Projects Screen
Select the number labels to learn about the options on the screen.
4: Show the files attached to a project. You can upload any type of file for
a project.
Scenario Options
The POWER tab displays the power connections of the selected system
model and the associated environmental specifications and energy costs.
It is categorized into four tabs: POWER INPUT, POWER OUTPUT,
ENVIRONMENTAL, and ENERGY COST.
The ENERGY COST tab displays the estimated power cost, depending on
a region’s power charges and currency.
Knowledge Check 10
a. CONNECTIVITY
b. EXPORT
c. POWERPOINT
d. EDITOR
The I/O workload characterization for the first use case is as follows:
Workload:
200K IOPS (with 10% growth)
2 ms latency
8 KiB I/O size
Random 50% read and 50% write
Split workload: Auto-optimal
The sizing activity has hints for guidance at each step. Select
the HINT icon to view the hints.
The second use case has the following I/O workload characterization:
The sizing activity has hints for guidance at each step. Select
the HINT icon to view the hints.
The third use case uses custom constraints and multiple block and file
workloads.
Constraints:
Maximum capacity utilization: 70%
Storage performance saturation: 70%
The sizing activity has hints for guidance at each step. Select
the HINT icon to view the hints.
The earlier use cases covered PowerStore T solutions. The fourth use
case will cover a PowerStore X solution with VM workloads.
The sizing activity has hints for guidance at each step. Select
the HINT icon to view the hints.
Select each sample to preview key slides from each presentation and
download the presentation for reference.
Cluster Information
Cluster information
Appliance Information
Appliance 1 configuration
Workload Information
Appliance 1 workload
Cluster Information
Cluster Information
Appliance 1 Information
Appliance 1 Information
Appliance 1 Workload
Appliance 1 Workload
Appliance 2 Information
Appliance 2 Information
Note that the power consumption and associated overheads for this
solution are different from those of the sample single appliance solution
because their workloads and capacity utilization are different.
PowerSizer output
PowerSizer output