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 you are billed per ECPU hour reserved from the time the built-in Tool is launched. ECPU usage is measured each second, in units of whole ECPUs and averaged across an hour. If your database is running for less than an hour or you change the number of ECPUs for only part of an hour, your built-in Tool ECPU usage is billed per second for the average ECPU consumption during that hour. The minimum ECPU consumption is one minute.

• 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:

For example, assume you allocate 4 ECPUs as the base ECPU count for the Autonomous Database instance, with compute auto-scaling disabled, and you use 8 ECPUs for Graph Studio with the maximum idle time set to 30 minutes. If you use Graph Studio for 30 minutes starting at 2 pm, your bill for the specified time period (2-3pm) is a total of 12 ECPUs. This sum includes the 4 base ECPUs plus the additional tools usage of 8 ECPUs for Graph Studio (including 30 minutes of actual usage and 30 minutes of idle time).

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 use the default 8 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 8 ECPUs for OML compute usage for 30 minutes plus 6 ECPUs for the database compute resources for the full hour, for a total of 14 ECPUs assuming no other tools are used in this period.

Note: 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. ECPU usage is measured each second, in units of whole ECPUs and averaged across an hour. If your database is running for less than an hour or you change the number of ECPUs for only part of an hour, it is billed per second for the average ECPU consumption during that hour. The minimum ECPU consumption is one minute.

Depending on the workload type of the Autonomous Database instance, built-in tool usage is charged to the following SKUs:

• Oracle Autonomous Transaction Processing – ECPU – BYOL
• Oracle Autonomous Data Warehouse – ECPU – BYOL
• Autonomous JSON Database – ECPU

See ECPU Compute Model Billing Information for details on built-in tools billing.