Help Center/ Scalable File Service/ Troubleshooting/ General-Purpose File System Performance Was Poor
Updated on 2025-12-10 GMT+08:00
View PDF
Share

General-Purpose File System Performance Was Poor

Symptom

Data was written slowly to a general-purpose file system, the file system performance cannot meet service requirements, or file transfer was slow.

Troubleshooting

Possible causes are described in order of how likely they are to occur.

If the fault persists after you have ruled out one cause, move on to the next one.

Table 1 Troubleshooting

Possible Causes

Solution

There are too many or too few concurrent requests.

Too many or too few concurrent requests may deteriorate the file system performance. Submit a service ticket.

The log file path contains variables.

If it takes a long time to write logs to the general-purpose file system using Nginx, do as follows:

  • Delete variables from the access_log directive and use a fixed path to store log files.
  • Set the log file descriptor cache using the open_log_file_cache command, which improves the performance of the log path containing variables.

The local network is faulty.

Rectify the network fault.

Submitting a Service Ticket

If the problem persists, submit a service ticket.