This topic describes Lindorm TSDB Serverless that is provided by ApsaraDB for Lindorm (Lindorm).
If you use Lindorm TSDB Serverless, you do not need to plan or purchase hardware resources, such as CPU and memory resources. You can subscribe to a specific number of capacity units (CUs) based on your business requirements. For more information about the billing items, see "Billing items" of this topic. The CUs are available after you purchase a subscription. Lindorm TSDB Serverless supports auto scaling. If your business requirements change, Lindorm TSDB Serverless allocates physical resources in the backend to meet your business requirements. This way, your system can scale on demand. This also reduces your O&M costs and system risks.
If you use Lindorm TSDB Serverless, you need to pay only for the used resources. This provides a more cost-effective solution for your business than the traditional mode.
Lightweight configuration for small and medium-sized enterprises
Lindorm TSDB Serverless is suitable for small and medium-sized enterprises. In serverless mode, you need to pay only for the used resources and do not need to purchase an entire cluster. If you use Lindorm TSDB Serverless for a short period of time, costs can be reduced to lower than 10% of the costs that are required when you use Lindorm TSDB. You can start or release a Lindorm TSDB Serverless instance within seconds. This allows you to use this service in a flexible manner.
Scheduled task processing
The high scalability of Lindorm TSDB Serverless makes it suitable to process scheduled tasks.
Fluctuating business workloads
For fluctuating business workloads, you need to prepare a large number of nodes and CUs that are required only during peak hours. This wastes a large amount of time, energy, and costs. For fluctuating business workloads, we recommend that you use Lindorm TSDB Serverless. This way, Lindorm automatically increases the number of CUs on demand to handle peak-hour traffic. To reduce costs, Lindorm automatically reduces the number of CUs during off-peak hours.
Business that requires zero O&M
The O&M team of Lindorm TSDB Serverless has accumulated years of technical expertise and can maintain, upgrade, optimize, and troubleshoot issues in Lindorm clusters in a professional manner. You do not need to worry about resource usage or software versions. This enables zero O&M for your clusters.
Enable Lindorm TSDB Serverless
An Alibaba Cloud account is created.
A virtual private cloud (VPC) is created. If no VPCs are available, log on to the VPC console to create a VPC.
The Lindorm console is logged on to.
Create a Lindorm instance that uses Lindorm TSDB Serverless
On the Instance list page in the Lindorm console, click Create to go to the ApsaraDB for Lindorm (Subscription) page.
Set Product Type to LindormServerless (Subscription).
Configure parameters. For more information about the parameters, see Create an instance.
After you configure the parameters, click Buy Now to go to the Confirm Order page. Confirm the parameter settings, and read and agree to Terms of Service. Then, click Pay to complete the payment.
Use Lindorm TSDB Serverless
You can use Lindorm TSDB Serverless in the same way as you use Lindorm TSDB.
For Lindorm TSDB Serverless, resources that are used by the read and write operations are measured in CUs. Lindorm calculates the number of CUs based on the following rules:
If the size of the data returned by a write operation is greater than 4 KB, Lindorm divides the actual data size by 4 KB and returns a value that is rounded up to the nearest integer. This value is the number of CUs that are calculated to be used by the write operation.
If the size of the data returned by a read operation is greater than 4 KB, Lindorm calculates the total size of data points, fields, and tags, divides the total size by 4 KB, and then returns a value that is rounded up to the nearest integer. This value is the number of CUs that are calculated to be used by the read operation. For example, you read subqueries 10 times in a second. In five of the read operations, each operation reads the data of 3.78 KB. In this case, the system divides 3.78 KB by 4 KB, rounds up the result, and then multiplies the result by 5. In the other five read operations, each operation reads the data of 4.26 KB. In this case, the system divides 4.26 KB by 4 KB, rounds up the result, and then multiplies the result by 5. The number of CUs used by 10 read operations in a second is calculated based on the following equation: (5 x 1) + (5 x 2) = 15. The system rounds 3.78 KB up as 1 CU used by the read operation, and rounds 4.26 KB up as 2 CUs used by the read operation.
For Lindorm TSDB Serverless, the used storage is calculated based on the size of compressed data that you write to a table. Lindorm adopts a log-structured merge-tree (LSM tree) and includes storage costs such as the costs of write-ahead logging (WAL). This way, the system does not delete the data that expires or you want to delete until the data is compacted. The storage is released only after the data is deleted.
Lindorm TSDB Serverless supports the subscription billing method.
To use the subscription billing method, you prepay for computing resources and storage resources. If the number of computing resources that you use exceeds the number of computing resources that you purchased,
QuotaExceeded is reported. If the number of storage resources that you use exceeds the number of storage resources that you purchased for a Lindorm TSDB Serverless instance, data cannot be written to the instance. You can reconfigure the number of CUs and disks based on your business requirements on the instance details page. The following examples are provided:
If you purchase 200 CUs of computing resources, you can use a maximum of 200 CUs each second. If more than 200 CUs are requested, the system triggers throttling. If you use less than 200 CUs each second, the idle CUs cannot be reserved for future use.
If you purchase 10 GB storage for a Lindorm TSDB Serverless instance and the used storage exceeds 10 GB, data cannot be written to the instance. If you use less than 10 GB storage, you still need to pay for 10 GB storage each month.
A query contains a maximum of 200 subqueries.
A subquery can be run in a maximum of 5,000 time series.
A subquery can retrieve a maximum of 25,000 data points.
The maximum number of queries per second (QPS) is 20.