tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Storage Class

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-12-26 16:35:08

How is INTELLIGENT TIERING billed?

INTELLIGENT TIERING fees include INTELLIGENT TIERING storage usage fees and INTELLIGENT TIERING object monitoring fees.
1. INTELLIGENT TIERING storage usage fees are charged differently depending on the storage tier of objects.
When objects are stored in the frequent access tier, STANDARD storage usage fees are charged.
When objects are stored in the infrequent access tier, STANDARD_IA storage usage fees are charged.
Note:
STANDARD and STANDARD_IA storage usage fees vary by region. For details about their pricing, see Product Pricing.
Request fees and traffic fees are also incurred during object upload and download. For the billing examples, see Traffic Fees and Request Fees.
2. INTELLIGENT TIERING object monitoring fees are charged based on the number of objects stored (excluding files smaller than 64 KB). For details about their pricing, see Product Pricing.
Sample
Assume that an organization has 100,000 objects (10 MB per object, 1 TB in total), and the data is stored in the INTELLIGENT TIERING storage class in Beijing region. If 20% of the objects (i.e., 20,000 objects) transition to the infrequent access tier every month, the object monitoring fees and storage usage fees for each month will be as follows:
Month
Object Monitoring Fees (USD)
INTELLIGENT TIERING Storage Usage Fees (USD)
STANDARD Storage Usage Fees (USD)
1
0.25
1024 x 0.024 = 24.58
1024 x 0.024 = 24.58
2
0.25
819.2 x 0.024 + 204.8 x 0.018 = 23.35
1024 x 0.024 = 24.58
3
0.25
655.36 x 0.024 + 368.64 x 0.018 = 22.36
1024 x 0.024 = 24.58
4
0.25
524.288 x 0.024 + 499.712 x 0.018 = 21.58
1024 x 0.024 = 24.58
5
0.25
419.4304 x 0.024 + 604.5696 x 0.018 = 20.95
1024 x 0.024 = 24.58
6
0.25
335.54432 x 0.024 + 688.45568 x 0.018 = 20.45
1024 x 0.024 = 24.58
As you can see, using INTELLIGENT TIERING reduces storage costs over time. Only a small amount of monitoring fees is incurred each month.

What types of objects is INTELLIGENT TIERING suitable for?

INTELLIGENT TIERING is suitable for large objects (such as audios, videos, and logs) whose access patterns change. Larger average object sizes mean that you pay less for monitoring per GB of objects. If your business has relatively fixed data access patterns, you can set lifecycle configuration to specify the time to transition objects to STANDARD_IA without the need to use INTELLIGENT TIERING.

How do I store objects in INTELLIGENT TIERING?

You can store objects in INTELLIGENT TIERING as follows:
Incremental objects: You just need to specify the storage class as INTELLIGENT TIERING when uploading objects.
Existing objects: You can modify the storage class to INTELLIGENT TIERING by using the COPY API. You can also use the lifecycle feature to transition STANDARD or STANDARD_IA objects to INTELLIGENT TIERING.
Note:
INTELLIGENT TIERING objects smaller than 64 KB will always be stored in STANDARD. For such objects, we recommend you upload them to the STANDARD, STANDARD_IA, ARCHIVE, or DEEP ARCHIVE storage class as needed to reduce costs.

How do I disable INTELLIGENT TIERING configuration?

INTELLIGENT TIERING configuration can't be disabled once enabled. If you don't need to store your objects in INTELLIGENT TIERING, you just need to specify the storage class as a non-INTELLIGENT TIERING class such as STANDARD, STANDARD_IA, ARCHIVE, or DEEP ARCHIVE when uploading objects.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan