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


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

SmartQoS Feature Guide
OceanStor Dorado V3 Series V300R001

This document is applicable to OceanStor Dorado5000 V3, Dorado6000 V3, and Dorado18000 V3. It describes the implementation principles and application scenarios of the SmartQoS 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 for Critical Services

This practice simplifies storage architecture but causes those services to compete for system resources, which compromises storage system performance.

To ensure the performance of critical services, you can:

  • Set I/O priorities.
  • Create a SmartQoS flow control policy.

The services processed in a storage system can be categorized into the following types:

  • Online transaction processing (OLTP) services that are critical and time-sensitive
  • Backup services that have a large data amount and are tolerant of latency
  • Mixed services of OLTP services (08:00 to 00:00) and backup services (00:00 to 08:00)

    This section uses a storage system processing the mixed services as an example. Table 1-2 lists the I/O characteristics of those two services.

Table 1-2 I/O characteristics of OLTP and backup


I/O Characteristic

Peak Hours of Operation


Random small I/Os, typically measured in IOPS

08:00 to 00:00


Sequential large I/Os, typically measured in bandwidth

00:00 to 08:00

  • Sufficient system resources must be reserved for those two services in their specific periods.
  1. You can adjust LUN I/O priorities to prioritize OLTP services.
    • Set the LUN I/O priority of OLTP services to high, ensuring the correct operating of OLTP services.
    • Set the LUN I/O priority of backup services to low, preventing backup services from occupying OLTP services' resources.
  2. To meet the requirements, you can create two SmartQoS policies.
    • SmartQoS flow control policy A limits the bandwidth of backup (for example, ≤ 50 MB/s) during 08:00 to 00:00, to reserve sufficient system resources for OLTP and ensure that the OLTP works normally in the daylight.
    • SmartQoS flow control policy B limits the IOPS of OLTP (for example, ≤ 200) during 00:00 to 08:00, to reserve sufficient system resources for backup and finish backing up at midnight.

Figure 1-4 illustrates this example of how the SmartQoS controls storage resources for OLTP and backup services.

Figure 1-4 Controlling storage resources for services

Ensuring Performance for High-Priority Subscribers

For cost saving, some subscribers have no dedicated storage systems. Instead, they prefer to run services on the storage platforms offered by a storage service provider. This choice lowers the total cost of ownership (TCO). However, services of different types and characteristics may encounter storage resource competition. 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. In this way, the storage service provider can offer sufficient resources for high-priority subscribers.

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

Table 1-3 Characteristics of subscribers


Quality Requirement

Subscriber A (gold subscriber)


Subscriber B (silver subscriber)


  1. You can adjust LUN I/O priorities to prioritize the services of high-priority subscribers.
    • Set the I/O priority of subscriber A to high, ensuring the correct operating of OLTP services.
    • Set the I/O priority of subscriber B to low, preventing its services from occupying subscriber A's resources.
  2. The provider can create separate SmartQoS policies for the two subscribers.
    • SmartQoS flow control policy A. This policy 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.
    • SmartQoS flow control policy B. This policy 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-5 illustrates this example of how SmartQoS controls storage resources for subscriber A and subscriber B.

Figure 1-5 Controlling storage resources for subscribers
Updated: 2018-10-19

Document ID: EDOC1000178797

Views: 14077

Downloads: 135

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next