Exclusive resource groups for DataService Studio
Exclusive resource groups for DataService Studio provide dedicated computing resources and isolated environments for high-concurrency API calls. Use them when external applications call APIs created in DataService Studio and require guaranteed queries per second (QPS) and high availability. This topic covers the performance metrics, billing standards, and lifecycle management of exclusive resource groups for DataService Studio.
Exclusive resource groups for DataService Studio are not recommended
DataWorks no longer recommends exclusive resource groups for DataService Studio. Use serverless resource groups instead. A single serverless resource group supports data synchronization, task scheduling and execution, and API service calls and management — replacing exclusive resource groups for scheduling, exclusive resource groups for Data Integration, exclusive resource groups for DataService Studio, and public resource groups.
Use cases
-
High-frequency, high-concurrency calls to DataService Studio APIs that require timely data returns.
-
Flexible adjustment of resource group size to match traffic demands.
-
Accessing data sources over the Internet, in Alibaba Cloud Virtual Private Clouds (VPCs), or in on-premises data centers (IDCs).
Limitations
-
Exclusive resource groups for DataService Studio use the subscription billing method. You cannot delete or release a resource group before it expires. After expiration, the service is stopped and the resource is released at a scheduled time.
Performance metrics
|
Resource group specifications |
Maximum queries per second (QPS)1 |
Service-Level Agreement (SLA) |
Supported regions |
|
api.s2.small |
500 |
99.95% |
|
|
api.s2.medium |
1000 |
99.95% |
|
|
api.s2.large |
2000 |
99.95% |
|
|
api.s1.small(New purchases not supported) |
500 |
99.95% |
|
|
api.s1.medium(New purchases not supported) |
1000 |
99.95% |
|
|
api.s1.large(New purchases not supported) |
2000 |
99.95% |
The QPS values are estimates based on the following assumptions:
-
Whether the API is generated in the code editor.
-
Whether the paging feature is enabled for API response results.
-
The average SQL execution time on the data source is 100 ms.
-
The average response size per API call is 3,000 bytes.
If your scenario differs significantly from these assumptions, join the DataWorks DingTalk group for specification recommendations based on your actual workload.
Billing standards
|
Region |
Specifications |
Price (CNY/month) |
|
China (Shenzhen) |
api.s2.small |
1205.00 |
|
api.s2.medium |
2410.00 |
|
|
api.s2.large |
4820.00 |
|
|
api.s1.small |
2186.00(New purchases not supported) |
|
|
api.s1.medium |
4372.00(New purchases not supported) |
|
|
api.s1.large |
8744.00(New purchases not supported) |
|
|
China (Beijing) |
api.s2.small |
1205.00 |
|
api.s2.medium |
2410.00 |
|
|
api.s2.large |
4820.00 |
|
|
api.s1.small |
2186.00(New purchases not supported) |
|
|
api.s1.medium |
4372.00(New purchases not supported) |
|
|
api.s1.large |
8744.00(New purchases not supported) |
|
|
China (Hangzhou) |
api.s2.small |
1205.00 |
|
api.s2.medium |
2410.00 |
|
|
api.s2.large |
4820.00 |
|
|
api.s1.small |
2186.00(New purchases not supported) |
|
|
api.s1.medium |
4372.00(New purchases not supported) |
|
|
api.s1.large |
8744.00(New purchases not supported) |
|
|
China (Shanghai) |
api.s2.small |
1205.00 |
|
api.s2.medium |
2410.00 |
|
|
api.s2.large |
4820.00 |
|
|
api.s1.small |
2186.00(New purchases not supported) |
|
|
api.s1.medium |
4372.00(New purchases not supported) |
|
|
api.s1.large |
8744.00(New purchases not supported) |
|
|
China (Zhangjiakou) |
api.s2.small |
835.00 |
|
api.s2.medium |
1670.00 |
|
|
api.s2.large |
3340.00 |
|
|
China (Hong Kong) |
api.s2.small |
2055.00 |
|
api.s2.medium |
4110.00 |
|
|
api.s2.large |
8220.00 |
|
|
Singapore |
api.s2.small |
1855.00 |
|
api.s2.medium |
3710.00 |
|
|
api.s2.large |
7420.00 |
Billing details
Change specifications
Upgrade the resource configuration of an exclusive resource group at any time in the DataWorks console. You pay only the price difference for the upgraded resources for the remaining subscription period. For more information, see Change specifications.
-
An upgrade changes the resource specifications of an existing order only — it does not add a new resource group.
-
The new configuration takes effect within 10 minutes of payment.
Renewal, service suspension, and release
Renew an exclusive resource group before it expires, or let the service be suspended and the resource group automatically released after expiration. For more information, see Expiration and renewal.
After a resource group is released, all tasks that rely on it can no longer run.