Rate This Document
Findability
Accuracy
Completeness
Readability

Creating a Storage I/O Diagnosis Task

The tool performs pressure tests on the storage I/O to obtain the maximum capability of the storage device and provide basic reference data for storage I/O performance tuning. It supports storage I/O pressure tests to obtain the maximum storage I/O capabilities, including throughput, IOPS, and latency.

Prerequisites

No nodes are in the Offline state.

Creating a Storage I/O Diagnosis and Analysis Task

  1. Click next to System Diagnosis.
  2. Set task parameters based on "Task Management" and Table 1.
    Figure 1 Creating a storage I/O diagnosis task
    Table 1 Parameters for creating a storage I/O diagnosis task

    Parameter

    Description

    Task Name

    Name of the task. The name must meet the following requirements:

    • Contain only letters, digits, and special characters (including @#$ %^&*()[]<>._-!-+ and spaces).
    • Contain 1 to 32 characters.

    Diagnosis Object

    Select Storage I/O.

    Diagnosis Type

    Storage I/O diagnosis type.

    By default, Common diagnosis is selected. The options are Common diagnosis, DPC diagnosis, or NFS diagnosis.

    Diagnosis Scenario

    Diagnosis scenario.

    By default, Performance pressure test is selected. The System load monitoring option is available only when Diagnosis Type is set to DPC diagnosis or NFS diagnosis.

    Pressure Test Object

    Pressure test object.

    • Node name
    • Node IP Address
    • Logical Drive Name/File Name: name of the logical drive or file to be tested. This parameter is mandatory when Diagnosis Type is set to Common diagnosis.
    • Mount Point: mount point for the pressure test. This parameter is mandatory when Diagnosis Type is set to DPC diagnosis or NFS Diagnosis.
    • Note: The fio process may fail to be stopped because a hard mount is used. The soft mount mode is recommended.
    NOTE:

    A file pressure test will damage existing data in the file. To avoid file overwriting, do not use an existing file as the pressure test object. In addition, do not use the drive with any file system mounted as the object for the logical drive pressure test.

    Key Metrics

    Pressure test parameters. Throughput, IOPS, and Latency are selected by default.

    • Request Block Size (KB)
    • Read/Write Mode
    • Read/Write Ratio
    • I/O Queue Depth
    • I/O Engine
    • Concurrency
    • Direct I/O
    • I/O Size (GB)
    • Test Duration (s)
    • Related Metrics
    • Operation

      You can click Edit or Delete to perform corresponding operations on a model.

      NOTE:

      By default, 12 test models are available for Common diagnosis and DPC diagnosis, and 6 test models are available for NFS diagnosis. You can add, edit, or delete test models as required. A maximum of 5 test models can be selected.

      You are advised to execute pressure tests in ascending order of the I/O size and task duration.

    Periodical Statistics

    You can enable or disable this function. If it is disabled, data is collected at an interval of 500 ms.

    Statistical Period (ms)

    Interval at which statistics are collected. The value ranges from 1 to 5000 ms.

    Size of the Collected File (MiB)

    Size of the file to be collected. The default value is 10 MiB. The value ranges from 1 MiB to 100 MiB.

    Sampling Interval (s)

    This parameter is mandatory when Diagnosis Scenario is set to System load monitoring.

    The default value is 1s. The sampling interval should be less than or equal to half of the test duration and cannot be longer than 10s.

    Task Execution

    Specifies whether to execute the task immediately. Only Execute now can be selected.

    NOTE:
    • A user can create a maximum of 20 scheduled tasks.
  3. Click OK.

    You can click the icons next to the task name to perform the following operations:

    • : cancels an analysis task. After an analysis task is stopped, the collected information will be deleted.
    • : restarts an analysis task. You can modify the task parameters and restart the analysis task.
    • : deletes an analysis task. After a task is deleted, all data of this task will be deleted. Exercise caution when performing this operation.
    • : modifies the task or report name. The report naming rule is the same as that of a task.

    The collection and analysis task will not be interrupted if you exit or switch to another page.

    After being authenticated, you can log in to the system again to view the execution progress of an ongoing task or the analysis report of a completed task.