Activation
When creating a model, select a MySQL cloud database. If the database is not activated, you can choose to activate it.
The activation process will take 2 to 3 minutes. Wait patiently.
After the activation is complete, you can continue to use the MySQL cloud database to create a model.
Specifications
The currently activated MySQL cloud database by default supports MySQL version 5.8. MySQL version selection will be supported in the future.
Automatic Start/Stop
The current MySQL cloud database is a serverless database. After a period (10 minutes) without access, the database will automatically pause until the next access request arrives.
During the pause period, the database will not consume computing resources.
When there is a new access request after pausing, the database takes some time to start up and process the request, so the response time for the first request will be longer.
You can also disable the automatic start/stop feature through database configuration. In this case, the database will continuously run and consume computing resources.
Usage-Related Descriptions
The MySQL cloud database is a serverless database. Related resource usage includes storage and computation.
Storage: the storage volume generated by the actual storage of tables and data.
Computation: the resource usage generated by compute instances running when the database processes requests and responses.
Storage Capacity
When using a MySQL cloud database, after the database is created, a small amount of storage volume will be generated due to the existence of system tables and system data. The storage volume increases as the tables and data in the database grow, and the storage volume will be continuously measured.
The storage volume is currently measured and billed as part of the overall storage volume in CloudBase. For detailed pricing and calculation methods, see CloudBase pricing documentation. Resource Usage
When a MySQL cloud database is used, if automatic start/stop is enabled, the compute instance will be shut down and reclaimed after a period of no database access, and will restart when the next request arrives. When the compute instance is shut down, resource usage is no longer calculated. When the instance starts running again, the total resource usage generated after startup will be calculated based on the instance's specifications and running duration. Additionally, if automatic start/stop is disabled, the database will continuously keep instances running. In this case, computing resource usage will be continuously generated.
On the other hand, the compute instance of the database will automatically scale based on pressure, number of connections, and other conditions during runtime. The scaling range is from instances with 0.25 cores and 1 GB of memory up to instances with specifications of 16 cores and 32 GB of memory. The current resource usage is calculated based on the specific instance specifications. For example, the resource usage of a 1-core instance running for 10 minutes will be 4 times that of a 0.25-core instance running for 10 minutes.
The resource usage of a MySQL cloud database is calculated daily, measured, and charged as part of the overall resource usage of CloudBase. For detailed pricing and calculation method, check CloudBase pricing documentation.