0 / 0
Watson Studio environments compute usage

Watson Studio environments compute usage

Compute usage is calculated by the number of capacity unit hours (CUH) consumed by an active environment runtime in Watson Studio. Watson Studio plans govern how you are billed monthly for the resources you consume.

Capacity units included in each plan per month
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

 

Capacity units included in each plan per month
Feature Lite Professional
Processing usage 10 CUH per month Unlimited CUH
billed for usage per month

 

Capacity units per hour for notebooks

Notebooks
Capacity type Language Capacity units per hour
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

 

The rate of capacity units per hour 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

    For example: The IBM Runtime 22.2 on Python 3.10 XS with 2 vCPUs will consume 1 CUH if it runs for one hour. If you have a project with 7 users working on notebooks 8 hours a day, 5 days a week, all using the IBM Runtime 22.2 on Python 3.10 XS environment, and everyone shuts down their runtimes when they leave in the evening, runtime consumption is 5 x 7 x 8 = 280 CUH per week.

    The CUH calculation becomes more complex when different environments are used to run notebooks in the same project and if users have multiple active runtimes, all consuming their own CUHs. Additionally, there might be notebooks, which are scheduled to run during off-hours, and long-running jobs, likewise consuming CUHs.

  • Default Spark environments by the hardware configuration size of the driver, and the number of executors and their size.

 

Capacity units per hour for notebooks with Decision Optimization

The rate of capacity units per hour consumed is determined by the hardware size and the price for Decision Optimization.

Decision Optimization notebooks
Capacity type Language Capacity units per hour
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

 

Capacity units per hour for notebooks with Watson Natural Language Processing

The rate of capacity units per hour consumed is determined by the hardware size and the price for Watson Natural Language Processing.

Watson Natural Language Processing notebooks
Capacity type Language Capacity units per hour
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

 

Capacity units per hour for Synthetic Data Generator

Capacity type Capacity units per hour
2 vCPU and 8 GB RAM 7

Capacity units per hour for SPSS Modeler flows

SPSS Modeler flows
Name Capacity type Capacity units per hour
Default SPSS XS 4 vCPU 16 GB RAM 2

 

Capacity units per hour for Data Refinery and Data Refinery flows

Data Refinery and Data Refinery flows
Name Capacity type Capacity units per hour
Default Data Refinery XS runtime 3 vCPU and 12 GB RAM 1.5
Default Spark 3.3 & R 4.2 2 Executors each: 1 vCPU and 4 GB RAM; Driver: 1 vCPU and 4 GB RAM 1.5

 

Capacity units per hour for RStudio

RStudio
Name Capacity type Capacity units per hour
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

 

Capacity units per hour for GPU environments

GPU environments
Capacity type GPUs Language Capacity units per hour
1 x NVIDIA Tesla V100 1 Python with GPU 68
2 x NVIDIA Tesla V100 2 Python with GPU 136

Runtime capacity limit

You are notified when you're about to reach the monthly runtime capacity limit for your Watson Studio service plan. When this happens, you can:

Remember: The CUH counter continues to increase while a runtime is active so stop the runtimes you aren't using. If you don't explicitly stop a runtime, the runtime is stopped after an idle timeout. During the idle time, you will continue to consume CUHs for which you are billed.

Track runtime usage for a project

You can view the environment runtimes that are currently active in a project, and monitor usage for the project from the project's Environments page.

Track runtime usage for an account

The CUH consumed by the active runtimes in a project are billed to the account that the project creator has selected in his or her profile settings at the time the project is created. This account can be the account of the project creator, or another account that the project creator has access to. If other users are added to the project and use runtimes, their usage is also billed against the account that the project creator chose at the time of project creation.

You can track the runtime usage for an account on the Environment Runtimes page if you are the IBM Cloud account owner or administrator.

To view the total runtime usage across all of the projects and see how much of your plan you have currently used, choose Administration > Environment runtimes.

A list of the active runtimes billed to your account is displayed. You can see who created the runtimes, when, and for which projects, as well as the capacity units that were consumed by the active runtimes at the time you view the list.

Learn more

Parent topic: Managing compute resources

Generative AI search and answer
These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more