Pivot3 X5-6500 - The IP Setup Utility

Setup & User Guide
77 |
DOC-246-GDE-Pivot3 Acuity 2.3 Setup & User Guide-v1.0.docx
Service
Level
Steady-state Behavior Degraded Behavior
Business
Critical
• Volumes in the Business Critical service
level receive the 2nd highest priority in
the system.
• If there is contention for performance
resources in the system, Business
Critical volume I/O will fall behind
Mission Critical volumes in priority.
• Performance of Non-Critical and then
Business Critical volumes may be
impacted to meet the Mission Critical
service level.
• If there are available resources in the
system, Business Critical volumes may
spike above the service level targets.
•
During a degraded state, Business
Critical volumes may take some of the
performance impact as required for
the system to continue to meet the
Mission Critical service level.
• Performance of Business Critical
volumes is “best-effort.”
• The system will impact the Non-
Critical volumes the most to attempt
to continue to meet the minimum
performance policy targets for
Business Critical volumes.
Non-
Critical
• Volumes in the Non-Critical service
level receive the lowest priority in the
system.
• If there is contention for performance
resources in the system, Non-Critical
volume I/O will fall behind Mission
Critical and Business Critical volumes
in priority.
• Performance of Non-Critical and then
Business Critical volumes may be
impacted to meet the Mission Critical
service level.
• If there are available resources in the
system, Non-Critical volumes may
spike above the service level targets.
•
During a degraded system, Non-
Critical volumes will take most of the
performance impact as required for
the system to continue to meet the
Mission Critical and Business Critical
service levels.
• Performance of Non-Critical volumes
is “best-effort”.
• The system will impact the Non-
Critical volumes the most to attempt
to continue to meet the steady-state
performance policy targets for Mission
Critical volumes and the minimum
performance policy targets for
Business Critical volumes.
BEST PRACTICE: Recommendations for assigning volumes to policies:
• Choose the highest priority applications and place the application volumes in Policy 1, Mission Critical service level.
• Do not assign all the volumes to Policy 1 as this will simply mean that all I/O is treated equally by the system. There
will be no real prioritization of I/O through the system.
• Typically, most customers have 20% of their volumes in the Mission Critical service level, 30-40% of their volumes in
Business Critical and the remaining volumes in Non-Critical.
• Applications that require low latency I/Os should be in either Policies 1 or 2. Applications that require low latency are
transaction based, like OLTP (online transaction processing) databases.
• Applications that are not as latency-sensitive should be placed in Polices 3, 4 or 5. Applications that fall into this
category are collaboration / file share type applications.