Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.
Scalable File Service
Scalable File Service
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
- Troubleshooting
-
FAQs
- Concepts
- Specifications
- Restrictions
- Networks
- Billing
-
Others
- How Do I Access a File System from a Server?
- How Do I Check Whether a File System on a Linux Server Is Available?
- What Resources Does SFS Occupy?
- Can a File System Be Accessed Across Multiple AZs?
- How Can I Migrate Data Between SFS and EVS?
- Can I Directly Access SFS from On-premises Devices?
- How Do I Delete .nfs Files?
- How Can I Improve the Copy and Delete Efficiency with an SFS Turbo File System?
- How Do Second- and Third-level Directory Permissions of an SFS Turbo File System Be Inherited?
On this page
Show all
Help Center/
Scalable File Service/
FAQs/
Others/
How Can I Improve the Copy and Delete Efficiency with an SFS Turbo File System?
How Can I Improve the Copy and Delete Efficiency with an SFS Turbo File System?
Updated on 2022-09-22 GMT+08:00
Common Linux commands, such as cp, rm, and tar, are executed sequentially. To take the concurrency advantage of cloud file systems, run commands concurrently to improve efficiency.
Parent topic: Others
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
