Different methods used by OceanStor 9000 to read and write large-scale small files and large files

2

Reading/writing large-scale small files and reading/writing large files are significantly different service models. OceanStor 9000 needs to have good I/O capabilities to read and write large-scale small files. These files have small sizes and large scales and therefore require low bandwidth usage which is not an important indicator for evaluating OceanStor 9000.
However, OceanStor 9000 needs to have good bandwidth usage and absolute bandwidth to read and write large files which have larger sizes and smaller scales than small files. In most cases, proof of concept (POC) or performance acceptance tests set requirements for the average read and write bandwidth and the maximum read and write bandwidth of OceanStor 9000.

Other related questions:
Methods used to optimize small files by using OceanStor 9000
To optimize small files, OceanStor 9000 shortens the I/O path of upper-layer services, aggregates small files on lower layers, decreases the number of disk I/Os and disk fragments, and simplifies processes to reduce unnecessary I/Os.

Can Different Engine IP Addresses Be Used to Read and Write the Same Shared File Concurrently?
Yes, they can. When different IP addresses are used to write the same shared file, only one IP address can write it successfully limited by the lock mechanism.

How can I upgrade the small and large systems of the MCU?
To upgrade the small and large systems of the MCU: Refer to the MCU upgrade guide as follows: Log in to Technical support website, search for the product name, for example, VP9660, and check the upgrade guide of the required version. Note: The small system needs to be upgraded independently for each board.

Method used to locate LUNs with poor read and write performance
Method used to locate LUNs with poor read and write performance: 1. The LUN write policy is write through. Locate the cause why the LUN write policy is write through. 2. If the host interface is iSCSI, check whether the network rate is 1 Gbit/s, whether the network is stable, and whether ping packets are lost. If the Fibre Channel or SAS network is used, log in to the storage's OSM page to check whether an alarm indicating that the front end encounters continuous error codes is reported. 3. Check whether slow disks exist in RAID groups. Specifically, run iostat -x 1 to check whether some disks differ from other disks (the util value of one or two disks is greater than that of other disks and reaches 100. If the util value of all disks in the RAID group reaches about 100, the configurations are incorrect and back-end disks are slow disks). If slow disks exist, replace them. 4. If a file system exists on the host, the file system produces enormous fragments when the disk space utilization rate exceeds 90%, causing the deterioration of read/write performance. You are advised to use disk space correctly.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top