No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

SmartQoS Feature Guide for File

OceanStor Dorado V3 Series V300R002

This document is applicable to OceanStor Dorado5000 V3, Dorado6000 V3, and Dorado18000 V3. It describes the implementation principles and application scenarios of the SmartQoS (for file) feature, and explains how to configure and manage SmartQoS.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Application Scenarios

Application Scenarios

SmartQoS dynamically allocates storage resources to ensure performance for critical services and high-priority subscribers.

Ensuring Performance of Critical Services

SmartQoS allows you to configure different performance goals for various services, ensuring the performance of critical services.

To ensure the performance of critical services, you can:

  • Set I/O priorities.
  • Create traffic control policies.

For example, a storage system processes both Online transaction processing (OLTP) and backup services, where:

  • OLTP services are critical and time-sensitive.
  • Backup services have a large data amount and are tolerant of latency.
Table 1-2 lists the I/O characteristics of those two services.
Table 1-2 I/O characteristics of OLTP and backup services

Application

I/O Characteristic

Peak Hours of Operation

OLTP

Random small I/Os, typically measured in IOPS

08:00 to 00:00

Backup

Sequential large I/Os, typically measured in bandwidth

00:00 to 08:00

Sufficient system resources must be reserved for these two services in their specific periods.

  1. You can adjust I/O priorities to prioritize OLTP services.
    • Set the I/O priority of OLTP services to high, ensuring the performance of OLTP services.
    • Set the I/O priority of backup services to low, preventing backup services from contending resources with OLTP services.
  2. You can create traffic control policies:
    • Create policies for limiting the maximum bandwidth and IOPS.
      • Traffic control policy A: limits the bandwidth for backup services (for example, ≤ 50 MB/s) from 08:00 to 00:00 to reserve sufficient system resources for OLTP services and ensure that the OLTP services work normally in the daylight.
      • Traffic control policy B: limits the IOPS of the OLTP services (for example, ≤ 200) from 00:00 to 08:00 to reserve sufficient system resources for backup services at night.
    • Create a policy for limiting the maximum latency.

      Traffic control policy C: limits the latency of the OLTP services (for example, ≤ 10 ms) from 08:00 to 00:00 to reserve sufficient system resources for the OLTP services and ensure that the OLTP services work normally in the daylight.

Figure 1-3 illustrates how SmartQoS controls storage resources for OLTP and backup services.

Figure 1-3 Controlling storage resources for services

Ensuring Performance for High-Priority Subscribers

To reduce the total cost of ownership (TCO), some subscribers run services on the storage platforms offered by a storage service provider instead of dedicated storage systems. However, services of different types and characteristics may contend for storage resources. High-priority storage service subscribers may fail to obtain desired resources.

With SmartQoS, providers can alleviate this competition by creating SmartQoS policies and setting I/O priority for subscribers, offering sufficient resources for high-priority subscribers.

For example, a storage service provider offers resources to subscribers A and B. Table 1-3 lists the characteristics of subscribers A and B.

Table 1-3 Characteristics of subscribers

Subscriber

Quality Requirement

Subscriber A (gold subscriber)

High

Subscriber B (silver subscriber)

Low

The provider can:

  1. Adjust I/O priorities to prioritize the services of high-priority subscribers.
    • Set the I/O priority of subscriber A to high, ensuring its service performance.
    • Set the I/O priority of subscriber B to low, preventing its services from contending with subscriber A for resources.
  2. Create separate traffic control policies for the two subscribers.
    • Traffic control policy A: limits the bandwidth of subscriber A (for example, ≤ 100 MB/s) to ensure service performance of subscriber A without affecting service performance of the storage system.
    • Traffic control policy B: limits the bandwidth of subscriber B (for example, ≤ 30 MB/s). This bandwidth is lower than that of subscriber A, to reserve enough system resources for other subscribers.

Figure 1-4 illustrates how SmartQoS controls storage resources for subscribers A and B.

Figure 1-4 Controlling storage resources for subscribers
Download
Updated: 2019-02-22

Document ID: EDOC1100067330

Views: 3516

Downloads: 19

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next