Billing details for watsonx.ai Studio tools
Learn about how compute usage is measured using capacity unit hours (CUH) consumed by an active environment runtime in watsonx.ai Studio.
For information on monitoring your account's resource usage, see Monitoring compute usage.
IBM watsonx.ai Studio plans govern how you are billed monthly for the resources you consume.
| Feature | Lite | Professional | Standard (legacy) | Enterprise (legacy) |
|---|---|---|---|---|
| Processing usage | 10 CUH per month |
Unlimited CUH billed for usage per month |
10 CUH per month + pay for more |
5000 CUH per month + pay for more |
CUH consumption for notebooks
| Capacity type | Language | Capacity unit hours |
|---|---|---|
| 1 vCPU and 4 GB RAM | Python R |
0.5 |
| 2 vCPU and 8 GB RAM | Python R |
1 |
| 4 vCPU and 16 GB RAM | Python R |
2 |
| 8 vCPU and 32 GB RAM | Python R |
4 |
| 16 vCPU and 64 GB RAM | Python R |
8 |
| Driver: 1 vCPU and 4 GB RAM; 1 Executor: 1 vCPU and 4 GB RAM | Spark with Python Spark with R |
1 CUH per additional executor is 0.5 |
| Driver: 1 vCPU and 4 GB RAM; 1 Executor: 2 vCPU and 8 GB RAM | Spark with Python Spark with R |
1.5 CUH per additional executor is 1 |
| Driver: 2 vCPU and 8 GB RAM; 1 Executor: 1 vCPU and 4 GB RAM; | Spark with Python Spark with R |
1.5 CUH per additional executor is 0.5 |
| Driver: 2 vCPU and 8 GB RAM; 1 Executor: 2 vCPU and 8 GB RAM; | Spark with Python Spark with R |
2 CUH per additional executor is 1 |
| Driver: 3 vCPU and 12 GB RAM; 1 Executor: 3 vCPU and 12 GB RAM; | Spark with Python Spark with R |
2 CUH per additional executor is 1 |
The rate of capacity unit hours consumed is determined for:
-
Default Python or R environments by the hardware size and the number of users in a project using one or more runtimes.
Formula:
Hours/day × Days × Number of users × CUH rate = Total CUH Total CUH × Service rate = Total chargeVariables used for the calculation Variable Description Hours/day Number of hours per day each user actively runs a notebook runtime Days Number of days in the billing period Number of users Number of users with active runtimes in the project CUH rate CUH per hour for the chosen environment (see table above) Service rate Current per-CUH price (for example, $1.02 USD) Example: You have a project with 7 users working on notebooks 8 hours a day, 5 days a week. All users use the
IBM Runtime 24.1 on Python 3.10 XSenvironment (2 vCPU, 8 GB RAM — CUH rate: 1), and everyone shuts down their runtimes at the end of the day.8 hours/day × 5 days × 7 users × 1 CUH = 280 CUH per week 280 CUH × $1.02 = $285.60 per weekThe CUH calculation becomes more complex when different environments are used in the same project, when users have multiple active runtimes, or when notebooks are scheduled to run during off-hours or as long-running jobs because each active runtime consumes its own CUH.
-
Default Spark environments by the hardware configuration size of the driver, and the number of executors and their size.
What are executors? In a Spark environment, the driver manages the overall execution of the Spark application (task scheduling and cluster communication), while executors are distributed worker processes that run the actual data-processing tasks in parallel. Each Spark environment template starts with one driver and one executor; you can add more executors to increase parallelism.
How the "CUH per additional executor" rate works: The CUH listed in the table is the baseline cost for the driver plus one executor. Each additional executor you add is charged at the "CUH per additional executor" rate shown in the same row.
Formula:
{: .codeblock} Total CUH = Base CUH + (Number of additional executors × CUH per additional executor)Example: Using
Driver: 1 vCPU and 4 GB RAM; 1 Executor: 1 vCPU and 4 GB RAM(base CUH: 1, CUH per additional executor: 0.5):- 0 additional executors:
1 + (0 × 0.5) = 1 CUH - 1 additional executor:
1 + (1 × 0.5) = 1.5 CUH - 2 additional executors:
1 + (2 × 0.5) = 2 CUH
- 0 additional executors:
CUH consumption for notebooks with Decision Optimization
The rate of capacity unit hours consumed is determined by the hardware size and the price for Decision Optimization.
| Capacity type | Language | Capacity unit hours |
|---|---|---|
| 1 vCPU and 4 GB RAM | Python + Decision Optimization | 0.5 + 5 = 5.5 |
| 2 vCPU and 8 GB RAM | Python + Decision Optimization | 1 + 5 = 6 |
| 4 vCPU and 16 GB RAM | Python + Decision Optimization | 2 + 5 = 7 |
| 8 vCPU and 32 GB RAM | Python + Decision Optimization | 4 + 5 = 9 |
| 16 vCPU and 64 GB RAM | Python + Decision Optimization | 8 + 5 = 13 |
CUH consumption for notebooks with Watson Natural Language Processing
The rate of capacity unit hours consumed is determined by the hardware size and the price for Watson Natural Language Processing.
| Capacity type | Language | Capacity unit hours |
|---|---|---|
| 1 vCPU and 4 GB RAM | Python + Watson Natural Language Processing | 0.5 + 5 = 5.5 |
| 2 vCPU and 8 GB RAM | Python + Watson Natural Language Processing | 1 + 5 = 6 |
| 4 vCPU and 16 GB RAM | Python + Watson Natural Language Processing | 2 + 5 = 7 |
| 8 vCPU and 32 GB RAM | Python + Watson Natural Language Processing | 4 + 5 = 9 |
| 16 vCPU and 64 GB RAM | Python + Watson Natural Language Processing | 8 + 5 = 13 |
CUH consumption for Pipelines Bash script
| Size | Capacity type | Capacity unit hours |
|---|---|---|
| XXS | 1 vCPU and 2 GB RAM | 0.5 |
| XS | 1 vCPU and 4 GB RAM | 0.5 |
| S | 2 vCPU and 8 GB RAM | 1 |
| M | 4 vCPU and 16 GB RAM | 2 |
| ML | 4 vCPU and 32 GB RAM | 2 |
Notes:
- The runtimes for Bash scripts stop automatically when processing is complete.
- Resource consumption is measured in seconds, with a minimum of 1 second. For example, if the execution time is 52.1 seconds, the charge is for 53 seconds.
CUH consumption in pipelines
Pipelines are used to run various assets, such as notebooks and scripts. While building a pipeline does not consume compute resources, running the pipeline does.
One specific case where CUH is explicitly charged is when running Bash script nodes in a pipeline. These scripts are executed using a selected hardware configuration, and the CUH charge is based on the execution time and the configuration used.
CUH consumption for SPSS Modeler flows
When you open an SPSS Modeler flow in a project, you choose an environment template for the runtime environment. The environment template specifies the type, size, and power of the hardware configuration, plus the software template. SPSS Modeler consumes compute resources as CUH from the watsonx.ai Studio service in projects.
After selecting an environment, any other SPSS Modeler flows opened in that project will use the same runtime. The hardware configuration of the available SPSS Modeler environments is preset and cannot be changed.
- How CUH is consumed
- When you open an SPSS Modeler flow and the runtime initializes, some CUH is consumed. However, running flows consumes more CUH than building the flows. There is no charge for defining a deployment or deployment job for an SPSS Modeler flow. You do that outside of the SPSS Modeler runtime. But there is a charge for running a deployment job or inferencing against the deployed asset.
You can select any of the following default environment templates for SPSS Modeler in a project. The included environment templates are listed under Templates on the Environments page on the Manage tab of your project.
| Name | Capacity type | Local storage | Capacity unit hours |
|---|---|---|---|
Default SPSS Modeler S |
2 vCPU and 8 GB RAM | 128 GB | 1 |
Default SPSS Modeler M |
4 vCPU and 16 GB RAM | 256 GB | 2 |
Default SPSS Modeler L |
6 vCPU and 24 GB RAM | 512 GB | 3 |
Changing the SPSS Modeler runtime
If you notice that processing is very slow, you can restart SPSS Modeler and select a larger environment runtime.
To change the SPSS Modeler environment runtime:
- Save any data from your current session before switching to another environment.
- Stop the active SPSS Modeler runtime under Tool runtimes on the Environments page on the Manage tab of your project.
- Restart SPSS Modeler and select another environment with the compute power and memory capacity that better meets your requirements.
CUH consumption for Data Refinery and Data Refinery flows
The rate of capacity unit hours consumed is determined by the environment's hardware configuration, size of the driver, and the number of executors and their size.
| Name | Capacity type | Capacity unit hours |
|---|---|---|
| Default Data Refinery XS runtime | 3 vCPU and 12 GB RAM | 1.5 |
| Default Spark 3.4 & R 4.3 | 2 Executors each: 1 vCPU and 4 GB RAM; Driver: 1 vCPU and 4 GB RAM |
1.5 |
CUH consumption for RStudio
| Name | Capacity type | Capacity unit hours |
|---|---|---|
| Default RStudio XS | 2 vCPU and 8 GB RAM | 1 |
| Default RStudio M | 8 vCPU and 32 GB RAM | 4 |
| Default RStudio L | 16 vCPU and 64 GB RAM | 8 |
CUH consumption for GPU environments
| Capacity type | GPUs | Language | Capacity unit hours |
|---|---|---|---|
| 1 x NVIDIA Tesla V100 | 1 | Python with GPU | 68 |
| 2 x NVIDIA Tesla V100 | 2 | Python with GPU | 136 |
Learn more
- watsonx.ai Studio service plans
- Service plans on AWS
- For details on computing resource allocation and consumption, see watsonx.ai Studio environments compute usage.