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).
Collecting Information

Collecting Information

The purpose of collecting information is to help understand and pinpoint what is causing the performance problem in the storage side. For example, details about I/O characteristics to help analyze the CPU performance of a controller more accurately and efficiently. Information that needs to be collected includes the types of services served by the storage system, I/O characteristics, and storage resource plan.

Service Types and I/O Characteristics

  • Service types include Oracle database OLTP and OLAP, VDI, and Exchange mail services. Analyzing service types helps determine whether you should pay attention to the IOPS or bandwidth and whether a low latency is required.
  • I/O characteristics include the I/O size, read/write ratio, cache hit ratio, and hotspot data distribution. You can use SystemReporter to observe I/O characteristics. Analyzing I/O characteristics helps understand whether the current service mainly involves sequential or random I/Os, large or small I/Os, and read or write I/Os.

Storage Resource Plan

You can use OceanStor DeviceManager or the Information Collection function of SmartKit (formerly named Toolkit, which is used as an example in this document) to collect information about the storage resource plan. A storage resource plan covers the following aspects:

  • Product models, specifications, and software versions

    To ensure load balancing among multiple controllers, each and every controller must have the same or similar numbers of interface module as well as front-end and back-end port connections. Otherwise, one controller may be overloaded whereas others are idle.

  • Number of front-end and back-end interface modules and number of connections

    In a bandwidth-sensitive scenario, the number of modules on the back-end interface must adequately support the bandwidth capacity required by those at the front-end interface, to enable optimal performance.

  • LUN properties, such as whether deduplication and compression are enabled and whether the owning controller of a LUN is consistent with its working controller.
  • Value-added feature configuration, for example, whether snapshot and remote replication are configured

    Value-added features involve more performance processes. On the one hand, a large number of metadata operations (such as initial LUN space allocation) are performed. On the other hand, a lot of non-host I/Os may be generated (for example, remote replication records and deletes data differences).

Translation
Download
Updated: 2019-07-17

Document ID: EDOC1100049152

Views: 11462

Downloads: 77

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