Compute resource options for Pipelines
When you run a pipeline in a project, most resources are tracked and billed for the components included in the pipeline. For example, running a notebook in a pipeline consumes resources for that notebook according to the environment specified. One resource explicitly charged for a pipeline is execution time running a Bash script node.
Default hardware configurations
You can specify a hardware configuration to use for executing a Bash script. The configuration you choose dictates the rate of CUH consumption billed to your Watson Studio plan.
Capacity units per hour for Bash script
| Size | Capacity type | Capacity units per hour |
|---|---|---|
| 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.
Compute usage in projects
Orchestration Pipelines consumes compute resources as CUH from the Watson Studio service.
You can monitor the total monthly amount of CUH consumption for the Watson Machine Learning service on the Resource usage page on the Manage tab of your project.
What consumes CUH?
Capacity unit hours (CUH) are consumed for running assets, not for working in tools. That is, there is no consumption charge for building a pipeline, but there is a charge for running the pipeline. CUH is also consumed by running Bash scripts in a pipeline.
Learn more
Parent topic: Choosing compute resources for tools