Torch Object Storage
Torch Object Storage
Torch Object Storage
Document
What's New
Announcements
Billing
Billable items
Billing method
Getting Started
User Guide
Working with buckets
Basic configurations
Managing lifecycle
Back-to-origin rules
Event notification
Intelligent Tiering
Domain management
Fault tolerance and disaster recovery
Cross-region replication
Same-region replication
Data redundancy
Image processing
ObjectSet
Working with objects
Managing folders
Monitoring and alerting
Metric monitoring
Access control
Bucket policies
Common configuration scenarios
Authorizing IAM users of the current account
Authorizing other accounts
Managing access via tools and SDKs
Managing public read access
Data security
Access points
Multi-region access points (MRAP)
Single-region access points (SRAP)
Converged access points (CAP)
DevMind
TOS accelerator
SenseFlow
TOS Agent
Data processing
Basic concepts
Image processing
Media processing
Document preview
Task processing
Data subscription
Flow control management
Quality of Service (QoS) policies
Hierarchical namespace (HNS)
User guide
Tool reference
Best practices
TOS Vectors
User guide
API reference
Vector bucket
Vector index
SDK reference
Python-Vectors
Vector bucket
Vector index
Java-Vectors
Vector bucket
Vector index
Node.js-Vectors
Vector bucket
Vector index
Tool Guide
tosutil
Common commands
Upload, download, and copy objects
Share objects
Auxiliary commands
Common examples
TOS Browser
FSX
FSX best practices
TOS PyTorch Connector
tosfsspec
TOS Import（will be deprecated soon）
API Reference
Signature Mechanism
The header contains a signature
Bucket
Basic Bucket Operations
Bucket Lifecycle
Access Monitor
Bucket ACL
Bucket CORS
Bucket Policy
Back-to-origin Rules
Bucket Replication
Versioning
Static Website
Event Notification
Custom Domain
Server-side encryption
Transfer Acceleration
Data Processing
Image processing
Media processing
Video transcoding
Audio transcoding
video to GIF
Document preview
File decompression
Log Storage
Retention Policy
Requester pays
TLS version
Object
Basic Object Operations
Object ACL
Fetch Object
Symbolic Link
WORM object
Multipart Upload
SDK Reference
Java
Pre-signing Mechanism
Bucket Interface
Basic Bucket Interface
Manage Bucket Configuration
Object Interface
Upload Object
Download Object
Upload and Download Speed Limit
Copy Object
List Object
Data Processing
Image Processing
Video Processing
Audio Processing
Log Configuration
Hierarchical Namespace
Bucket base interface
Introduction to Typical Scenes
Python
Data processing
Pre-signature mechanism
Bucket interface
Basic bucket interface
Manage bucket configuration
Object interface
Upload object
Download object
Copy object
List objects
Introduction to typical scenes
C
Object Interface
Upload object
C++
Pre-signature Mechanism
Bucket Interface
Basic Bucket Interface
Manage Bucket Configuration
Object Interface
Upload Object
Download Object
Copy Object
List Objects
Data Processing
Go
Object Interface
Upload Object
Download Object
Copy Object
List Objects
Manage Objects
Bucket Interface
Manage Bucket Configuration
Data Processing
Log Configuration
Introduction to Typical Scenes
Pre-signature Mechanism
Node.js
Pre-signature Mechanism
Bucket Interface
Basic Bucket Interface
Manage Bucket Configuration
Object Interface
Upload object
Download object
Copy object
List objects
Data Processing
Image Processing
Introduction to Typical Scenes
Browser.js
Pre-signature Mechanism
Upload Object
Download Object
Copy Object
List Objects
Manage Objects
Data Processing
.NET
Bucket Interface
Object Interface
Upload Object
Download Object
List Objects
Introduction to Typical Scenes
PHP
Bucket Interface
Object Interface
Download Object
Data Processing
Exception Handling
Android
Bucket Interface
Object Interface
Upload Object
Download Object
Exception Handling
iOS
Bucket Interface
Object Interface
Upload Object
Download Object
Harmony
Pre-signature Mechanism
Bucket Interface
Object Interface
Upload Object
Download Object
List Objects v2
Introduction to Typical Scenarios
Rust
Pre-signing mechanism
Bucket interface
Basic bucket operations
Lifecycle rules
Bucket ACLs
Cross-origin resource sharing
Bucket inventory
Back-to-origin rules
Bucket replication
Static website hosting
Event notification
Custom domain
Server-side encryption
Object interface
Basic operation
Access control
Error Codes
01-SERVICE_ERROR
02-AUTH
03-ACCESS_CONTROL
04-QOS
05-REQUEST
06-BUCKET
07-LIFECYCLE
08-ACL
09-CORS
10-POLICY
11-MIRROR
12-REPLICATION
13-WEBSITE
14-NOTIFICATION
15-ENCRYPT
16-CUSTOMDOMAIN
17-OBJECT
18-TAG
19-MULTIPART
20-STORAGE_CLASS
21-CALLBACK
22-DATA_PROCESS
23-BATCH
24-STORAGE_LENS
25-INVENTORY
26-DIRECTORY_BUCKET
FAQ
Best Practices
AIGC-Doubao LLMs
Accessing TOS with third-party tools
Granting temporary access
Data migration
Data processing
Checking data integrity
Performance optimization
- Documentation
Torch Object StorageBest PracticesPerformance optimizationBest practices for optimizing performance
Copy page
Download PDFPerformance optimization
Best practices for optimizing performance
Copy pageDownload PDFBest practices for optimizing performance
This topic describes how to achieve high performance for applications with TOS implementations.
Background information
TOS is a distributed object storage product designed for scenarios involving massive data. To provide applications with a high level of service, TOS offers linear performance scalability and dynamic data load balancing. Data partitioning and indexing are based on the UTF-8 encoding of bucket name + object name. In sequential read/write mode, TOS limits QPS to 2,000. For more information about TOS constraints, see Limits.
If you use sequential prefixes in your naming convention for objects (e.g., timestamps or alphabetical order), requests may concentrate on a specific shard. This creates hotspots. These hotspots are subject to the storage medium's read/write upper limits, which may increase access delays. You can apply the methods discussed in this topic to improve program performance.
warning
Performance optimization occurs gradually when reading or writing objects, rather than taking effect immediately. You may still encounter some errors after optimizing sequential prefixes, but these errors will disappear once the optimization is complete.
Optimization methods
To avoid the above-mentioned issues, we recommend that you consider the following optimizations when designing your application:
Handling hotspots caused by adjacent objects
- Write data from different businesses to different buckets.
- bucket:logobject:20220610-001.log.tar.gz20220610-002.log.tar.gz20220610-003.log.tar.gz......20220610-0xx.log.tar.gz
- bucket:metaobject:20220610-001.log.meta20220610-002.log.meta20220610-003.log.meta......20220610-0xx.log.meta
- Store buckets with sequential prefixes in different buckets.
- If a bucket still has massive sequential objects, name them in the following ways.
- Add a random prefix. For example, calculate a hash of the object name, then use a segment of the hash value between two and ten characters long as the object's prefix.
- //Original20220610-001.log.tar.gz//sha256:fa473ff003b91aa20239e20e41...20220610-002.log.tar.gz//sha256:dba85a4f69850bd8b7ba6fbe79...20220610-003.log.tar.gz//sha256:bd6665a44717e3bda18d12ea51.........20220610-0xx.log.tar.gz//sha256:a70364eaa3ce1b037c5707b06e...//After distribution fa473f-20220610-001.log.tar.gzdba85a-20220610-002.log.tar.gzbd6665-20220610-003.log.tar.gz......a70364-20220610-0xx.log.tar.gz
- Reverse the sequential object prefix. For example, reverse the date in the object name.
- //Original20220610-001.log.tar.gz20220610-002.log.tar.gz20220610-003.log.tar.gz......20220610-0xx.log.tar.gz//After reversion100-01602202.log.tar.gz200-01602202300-01602202......1xx-01602202
Handling hotspots caused by the same object
If your application sends many requests to the same object concurrently, the access speed will be subject to the TOS bandwidth and region restrictions. We recommend that you use Volcano Engine's Content Delivery Network (CDN) to improve performance while reducing your costs. For more information on accessing TOS through CDN, see Accelerating access to TOS resources using CDN.
Addressing TOS server-side throttling
TOS adopts server-side throttling so that all users can have a positive experience. For more information on TOS throttling, see Limits. The TOS throttling mechanism is explained below.
- List operations: TOS is a key-value storage service and provides list APIs for better O&M. However, we recommend that you not rely heavily on these APIs in your application. Particularly in scenarios involving frequent writes and paginated listing, your application will not be able to detect newly written or deleted objects from the previous page in real time, potentially leading to errors.
- Read and write operations: Even after implementing the anti-hotspot optimizations mentioned above, if you continue to frequently trigger TOS throttling, we recommend designing your application to avoid concurrent request peaks.
tip
When a throttling event occurs, TOS explicitly responds with a 429 status code. To avoid TOS throttling, we recommended that your application proactively implement back-off or rate limiting strategies. For back-off methods, see SDK documentation.
Adjusting TOS server-side throttling limits
If you are still not satisfied with your application's performance after applying the above optimizations, submit a ticket to request an increased throttling limit.
Last updated: 2025.11.18 14:49:33
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
