FeatureStore incurs resource fees when you configure a data source, install the FeatureStore Python SDK in DataWorks, or train models. You are charged for the resources that FeatureStore uses, based on the billing rules of the products that provide those resources.
Data source fees
The fees for a FeatureStore data source depend on the data source type: a FeatureDB data source is billed by request volume and stored data, and a Hologres data source is billed by the Hologres instance that you purchase.
FeatureDB data source
When you configure a FeatureDB data source, fees are incurred for writing, reading, and storing feature data. The following table describes the billing items and the unit price in each region group.
Billing item | Description | Fees in China (Beijing), China (Shanghai), China (Hangzhou), and China (Shenzhen) | Fees in China (Hong Kong), Singapore, US (Silicon Valley), and Germany (Frankfurt) |
Write fees | Fees are calculated based on write request units. Every 64 KB of the request body counts as one request, and fees are charged per 10,000 requests. | USD 0.02271 per 10,000 requests | USD 0.03986 per 10,000 requests |
Read fees | Fees are calculated based on read request units. Every 128 KB of returned data volume counts as one request, and fees are charged per 10,000 requests. | USD 0.01135 per 10,000 requests | USD 0.01994 per 10,000 requests |
Storage fees: Disk storage | Fees are charged per GiB per hour. | USD 0.00032 per GiB-hour | USD 0.00026 per GiB-hour |
Storage fees: Memory storage | Fees are charged per GiB per hour. | USD 0.00931 per GiB-hour | USD 0.01516 per GiB-hour |
Hologres data source
When you configure a Hologres data source, you must purchase a Hologres instance, which incurs Hologres resource fees. For pricing information, see Hologres billing overview.
DataWorks resource fees
When you install the FeatureStore Python SDK in DataWorks, you must purchase an exclusive resource group, which incurs DataWorks resource fees. For pricing information, see Billing of DataWorks exclusive resource groups.
MaxCompute fees
When FeatureStore runs and exports TrainSet sample tables, it uses MaxCompute, which incurs fees for MaxCompute public resources. For details, see MaxCompute billing overview.
MaxCompute fees consist of three parts: Computing Resources fees, storage resources fees, and resources for data uploads and downloads fees. PAI training tasks usually do not involve resources for data uploads and downloads.
Where the fees appear on your bill
After you use the pay-as-you-go billing method, the bills for algorithm tasks appear under PAI in compute resource fees, and the bills for other tasks, such as SQL tasks, appear under MaxCompute.