Hologres provides the Serverless Computing feature to allow you to run big SQL jobs in a fully managed serverless computing resource pool. In this case, you do not need to reserve computing resources that have fixed specifications for the big SQL jobs. You can isolate serverless computing resources for different SQL jobs to prevent resource contention and mutual interference. Big SQL jobs include SQL jobs that generate large CPU or memory overheads.
You will be charged for the use of the Serverless Computing feature from July 1, 2024 (UTC+8). For more information, see Billing overview.
Description
If you do not enable the Serverless Computing feature, you must reserve sufficient computing resources to run big SQL jobs. In most cases, big SQL jobs are run only during a specific period of time in a day, and the reserved resources are idle during the rest time of the day. This causes a waste of reserved resources. In addition, big SQL jobs compete for resources and interfere with each other because reserved computing resources are not isolated. This may lead to performance jitter.
After you enable the Serverless Computing feature, big SQL jobs can be run in a serverless computing resource pool that is independent of the exclusive resources of your instance. This prevents resource contention and resource waste. You do not need to reserve computing resources of exclusive instances for big SQL jobs. The stability of big SQL jobs is significantly improved.
The following figure shows the architecture of the Serverless Computing feature.
Scenarios
The Serverless Computing feature is suitable for the following scenarios:
Out of memory (OOM) errors frequently occur in big SQL jobs, and you want to improve the job success rate and instance stability.
Scenario description: The exclusive instance in use provides a small amount of exclusive computing resources. OOM errors frequently occur when you run big SQL jobs, such as importing or querying a large amount of data.
Optimization suggestion: We recommend that you use serverless computing resources to run the big SQL jobs. The maximum amount of available serverless computing resources is three times the amount of computing resources of an exclusive instance. During the job runtime, the serverless computing resources cannot be used by other jobs. This significantly improves the success rate of big SQL jobs and the stability of production instances.
A large amount of resources of your instance are idle during off-peak hours, and you want to improve resource utilization and reduce costs.
Scenario description: The instance is scaled out to support specific low-frequency big SQL jobs. The total runtime of the big SQL jobs is less than 8 hours per day.
Optimization suggestion: We recommend that you use serverless computing resources to run the big SQL jobs and scale in the instance to decrease the amount of reserved computing resources. This significantly improves the resource utilization of the exclusive instance. You are no longer charged for large amounts of idle resources. You are charged only for the amount of serverless computing resources that are consumed by big SQL jobs.
References
For more information about the usage and billing of serverless computing resources, see Resource consumption and billing.
For more information about how to enable, disable, and use the Serverless Computing feature and perform other related operations, see User guide for Serverless Computing.