Oracle Autonomous Database Serverless Billing for Database Tools
The following built-in tools have separate, configurable compute resource limits:
- Graph Studio
- Oracle Machine Learning
- Data Transforms
For these tools compute resource usage does not use the database's base compute, as specified with the ECPU count, or any auto-scaled ECPUs. These tools have separate ECPU allocation, independent from the database compute ECPU count (and independent of Compute auto scaling).
For Graph Studio, Oracle Machine Learning, and Data Transforms, the ECPU count and Maximum idle time configuration options let you specify compute resource allocation for the VMs that run the associated built-in tool. When you configure these built-in tools, the values for these configuration options mean the following in terms of resource usage and billing:
-
You do not pay for a tool's ECPU allocation if you do not use the tool.
-
The VMs associated with a tool are provisioned when you start using a tool. For example, if Graph Studio is disabled, billing does not begin when you enable the tool. Billing begins when you start using Graph Studio.
-
The ECPU count specifies the compute resource allocation that is dedicated to the tool. The value you enter for ECPU count applies in addition to the database ECPU count you specify for the instance. After you start using a tool with a specified ECPU count, you are billed per ECPU hour reserved from the time the built-in tool is launched.
-
Billing stops for a built-in tool's allocated ECPUs when the built-in tool is disabled, the instance stops or is terminated, or when the built-in tool is idle for more than the specified Maximum idle time. The default maximum idle times depend on the tool:
-
The default maximum idle times depend on the built-in database tool:
- Graph Studio: 240 minutes
- Oracle Machine Learning User Interface: 60 minutes
- Data Transforms: 10 minutes
For example, assume you allocate 4 ECPUs, as the base ECPU count, for the Autonomous Database instance, with compute auto-scaling disabled, and 2 ECPUs for Graph Studio and set the maximum idle time to 30 minutes. Using Graph Studio for 30 min between 2 pm and 3 pm, your bill for the specified time period (2-3pm) is 4 ECPUs plus the additional tool usage for the Graph Studio usage of 2 ECPUs, which is a total of 6 ECPUs, assuming no other tools are used in this period.
As another example, assume you allocate 6 ECPUs, as the base ECPU count, for the Autonomous Database instance, with compute auto-scaling disabled, and you configure 4 ECPUs for Oracle Machine Learning (OML) with the maximum idle time set to 15 minutes. When the database is open and available for the hour between 2 to 3 pm, and you use OML for 15 min starting at 2 pm, with the specified 15 minute maximum idle time, you are charged for 4 ECPUs for OML compute usage for 30 minutes plus 6 ECPUs for the database compute resources for the full hour, for a total of 8 ECPUs assuming no other tools are used in this period.
Note: billing is per minute.
Built-in tools do not have separate, configurable compute resource limits. The built-in tools use compute from the database's selected OCPU count. Tool usage may also use auto-scaled OCPUs, if necessary.
Parent topic: How Is Autonomous Database Billed?