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

Performance Monitoring Guide

OceanStor Dorado V3 Series V300R002

This document describes performance monitoring of storage systems, including the monitoring method, indicator planning, configuration monitoring, and problem diagnosis.
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).
Checking the Multipathing Parameter Settings

Checking the Multipathing Parameter Settings

If the load balancing mode or algorithm, or other parameters of multipathing software are set inappropriately, the I/O pressure on links will be imbalanced or the sequence of I/Os will be affected. These prevent optimal performance delivery and adversely affect bandwidth capability.

  • On a Window host, use UltraPath Console to query the multipathing parameter settings.

    Operation path: System > Global Settings

  • On a Linux host, query the multipathing parameter settings by running upadmin show upconfig.
    # upadmin show upconfig 
    ======================================================= 
    UltraPath Configuration 
    ======================================================= 
    Basic Configuration 
        Working Mode : load balancing within controller 
        LoadBalance Mode : min-queue-depth 
        Loadbanlance io threshold : 1 
        LUN Trespass : on 
     
    Advanced Configuration 
        Io Retry Times : 10 
        Io Retry Delay : 0 
        Faulty path check interval : 10 
        Idle path check interval : 60 
        Failback Delay Time : 600 
        Io Suspension Time : 60 
        Max io retry timeout : 1800 
     
    Path reliability configuration 
        Timeout degraded statistical time : 600 
        Timeout degraded threshold : 1 
        Timeout degraded path recovery time : 1800 
        Intermittent I/O error degraded statistical time : 300 
        Min. I/Os for intermittent I/O error degraded statistical : 5000 
        Intermittent I/O error degraded threshold : 20 
        Intermittent I/O error degraded path recovery time : 1800 
        Intermittent fault degraded statistical time : 1800 
        Intermittent fault degraded threshold : 3 
        Intermittent fault degraded path recovery time : 3600 
        High latency degraded statistical time : 300 
        High latency degraded threshold : 1000 
        High latency degraded path recovery time : 3600 
     
    HypperMetro configuration 
        HyperMetro Primary Array SN : Not configured 
        HyperMetro WorkingMode : read write within primary array 
        HyperMetro Split Size : 128MB
  • On an AIX host, query the multipathing parameter settings by running upadm show upconfig.
    # upadm show upconfig 
    ======================================================= 
    UltraPath Configuration 
    ======================================================= 
    Basic Configuration 
        Working Mode : load balancing within controller 
        LoadBalance Mode : min-queue-depth 
        Loadbanlance io threshold : 1 
        LUN Trespass : on 
     
    Advanced Configuration 
        Io Retry Times : 10 
        Io Retry Delay : 0 
        Faulty path check interval : 10 
        Idle path check interval : 60 
        Failback Delay Time : 600 
        Io Suspension Time : 60 
        Max io retry timeout : 1800 
     
    Path reliability configuration 
        Timeout degraded statistical time : 600 
        Timeout degraded threshold : 1 
        Timeout degraded path recovery time : 1800 
        Intermittent I/O error degraded statistical time : 300 
        Min. I/Os for intermittent I/O error degraded statistical : 5000 
        Intermittent I/O error degraded threshold : 20 
        Intermittent I/O error degraded path recovery time : 1800 
        Intermittent fault degraded statistical time : 1800 
        Intermittent fault degraded threshold : 3 
        Intermittent fault degraded path recovery time : 3600 
        High latency degraded statistical time : 300 
        High latency degraded threshold : 1000 
        High latency degraded path recovery time : 3600 
        Sensitive delayed degraded threshold : 30000 
        Sensitive delayed degraded recovery time : 120 
     
    HyperMetro configuration 
        HyperMetro Primary Array SN : Not configured 
        HyperMetro WorkingMode : read write within primary array 
        HyperMetro Split Size : 128MB
  • On a VMware ESXi host, query the multipathing parameter settings by running esxcli upadm show upconfig.
    # esxcli upadm show upconfig 
    ======================================================= 
    UltraPath Configuration 
    ======================================================= 
    Basic Configuration 
        Working Mode : load balancing within controller 
        LoadBalance Mode : round-robin 
        Loadbanlance io threshold : 1 
        LUN Trespass : on 
     
    Advanced Configuration 
        Io Retry Times : 10 
        Io Retry Delay : 0 
        Faulty path check interval : 10 
        Idle path check interval : 60 
        Failback Delay Time : 0 
        Max io retry timeout : 1800 
     
    Path reliability configuration 
        Timeout degraded statistical time : 600 
        Timeout degraded threshold : 1 
        Timeout degraded path recovery time : 1800 
        Intermittent IO error degraded statistical time : 300 
        Min. I/Os for intermittent IO error degraded statistical : 5000 
        Intermittent IO error degraded threshold : 20 
        Intermittent IO error degraded path recovery time : 1800 
        Intermittent fault degraded statistical time : 1800 
        Intermittent fault degraded threshold : 3 
        Intermittent fault degraded path recovery time : 3600 
        High latency degraded statistical time : 300 
        High latency degraded threshold : 1000 
        High latency degraded path recovery time : 3600 
        Sensitive delayed degraded threshold : 30000 
        Sensitive delayed degraded recovery time : 120 
     
    APDtoPDL configuration 
        APD to PDL Mode : off 
        APD to PDL Timeout : 10 
     
    HyperMetro configuration 
        HyperMetro Primary Array SN : Not configured 
        HyperMetro WorkingMode : read write within primary array 
        HyperMetro Split Size : 128MB     
NOTE:

For details about the query methods used in other operating systems, see the UltraPath User Guide intended for those operating systems.

Load Balancing Mode

UltraPath V100R008 provides the following load balancing modes:

  • Intra-controller load balancing
  • Inter-controller load balancing

By default, intra-controller load balancing is used. If inter-controller load balancing is enabled, UltraPath uses all paths to deliver I/Os without considering the preferred and non-preferred controllers of a LUN. Inter-controller load balancing is suitable when the load must be balanced among all logical links. Intra-controller load balancing should be selected in most cases for high performance and to prevent I/O forwarding.

Load Balancing Algorithm

If the load balancing algorithm of multipathing software is inappropriate, the I/O pressure among links may also be imbalanced, preventing the optimal performance from being offered. UltraPath V100R008 supports three load balancing policies: min-queue-depth, round-robin, and min-task.

  • min-queue-depth: This policy collects statistics about the number of I/Os queuing in each path in real time and sends I/Os to the shortest path accordingly. When an application server sends I/Os to a storage system, the path with the minimum I/O queue takes precedence over other paths in sending I/Os.

    min-queue-depth is the default path selection algorithm and provides the optimal performance in most cases.

  • round-robin: I/Os sent by an application server to a storage system for the first time are transmitted over path 1, I/Os sent for the second time are transmitted over path 2, and so on in a sequential pattern.

    The round-robin policy is typically used with the inter-controller load balancing process. In most of these cases, the bandwidth performance is adversely affected because I/Os are sent in sequence to each logical link without consideration of the load. As a result, a link may become congested with too much pressure, which affects the sequence of I/Os.

  • min-task: When an application server sends I/Os to a storage system, the overall amount of data is calculated based on the block size of each I/O request. Then, I/Os are sent to the path that has the minimum amount of data.

    The min-task policy is seldom used. It has a similar performance impact as the min-queue-depth policy.

Load Balancing Consecutive I/O Quantity

Load balancing consecutive I/O quantity indicates the number of I/Os sent by a host at a time over each selected path. For example, in UltraPath for Linux, Loadbalance io threshold indicates the consecutive I/O quantity. The default value is 100, indicating that a host sends 100 I/Os over each selected path. Controlling the consecutive I/O quantity can improve efficiency through combining I/Os. For example, a Linux block device can combine several I/Os destined for consecutive addresses, into a large I/O to send to the storage system.

In certain scenarios, if the consecutive I/O quantity is set to an inappropriate value, the performance is adversely affected.

  • In a Windows operating system, the default value of the consecutive I/O quantity is 1. Do not change the value because Windows does not have a block device and will not combine I/Os.
  • In a Linux operating system, set the consecutive I/O quantity to a small value for large-I/O scenarios. The maximum I/O size adopted by a Linux block device is 512 KB, even if I/Os are combined. If I/Os of over 512 KB are sent, they will not be combined. In this case, set the consecutive I/O quantity to 1.
  • If I/Os are randomly sent, they almost cannot be combined. To reduce the overhead, set the consecutive I/O quantity to 1.
Translation
Download
Updated: 2019-07-17

Document ID: EDOC1100049152

Views: 11368

Downloads: 76

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next