Yandex Managed Service for YTsaurus pricing policy
Note
The service is at the Preview stage.
In this section, you can find the Managed Service for YTsaurus pricing policy and effective prices for its resources. For other Yandex Cloud resources consumed while using the service you pay as per their pricing plans.
Tip
The prices for service products are also available in the price list.
Note
Currency of Service rates (prices) depends on the company you made a contract with:
- Prices in US dollars are applicable to customers of Iron Hive doo Beograd (Serbia) or Direct Cursus Technology L.L.C. (Dubai).
- Prices in Russian roubles are applicable to customers of Yandex.Cloud LLC.
All prices below do not include VAT.
Cluster status
The prices apply differently depending on the cluster status:
- For a
Runningcluster, you pay for both the computing resources and storage size. - For a
Stoppedcluster, you only pay for your storage size.
What goes into the cost of using Managed Service for YTsaurus
When using Managed Service for YTsaurus, you pay for:
- Disk type and storage size.
- Computing resources allocated to the cluster components.
- Number of vCPUs.
- Amount of RAM.
- Outgoing traffic from Yandex Cloud to the internet.
In all calculations: 1 GB = 230 bytes, 1 MB = 220 bytes.
Using cluster components
The component operation cost is charged per hour based on what computing resources you allocate for it. You can check the supported component configuration options in the relevant section and see prices for using vCPUs and RAM in the Prices section.
You can choose the configuration option for exec and tablet nodes based on the expected load. The number of service components, such as master, storage, system, and proxy nodes, depends on the cluster configuration and is applied automatically. See below for the minimum setup of service components required for a YTsaurus cluster to run:
-
Master node: Three configuration instances, 4 vCPUs and 12 GB RAM.
-
System node: Two configuration instances, 24 vCPUs and 64 GB RAM.
-
Proxy node: Two instances: One HTTP proxy and one RPC proxy.
-
Service tablet node: Two
c8-m16configuration instances, 8 vCPUs and 16 GB RAM. Service tablet nodes are used for system dynamic tables. -
Storage node: The number of storage nodes depends on the storage configuration and is applied as per below.
Defining the number of storage nodes in a cluster
- For each
HDD, there is one storage node with 4 vCPUs and 8 GB RAM. - For each
SSDornon-replicated SSD, there is one storage node with 8 vCPUs and 8 GB RAM.
Additionally, there are three service storage nodes with 8 vCPUs and 8 GB RAM. They are used to store chunks and logs of system dynamic tables.
- For each
The minimum billing unit is one minute (for example, 90 seconds of the component operation cost is same as two minutes).
Disk space usage
You are charged for the following:
-
The size of the storage for the exec node, where various jobs are run.
-
The size of the storage for the service storage nodes that stores chunks and logs of system dynamic tables. This size is applied automatically, with three non-replicated SSDs, 93 GB each.
-
The size of storage for the storage node that houses the data of all YTsaurus objects that are created during its operation. This storage may consist of one or two disks. The number and size of such disks are defined as per below.
Defining the number of disks in storage nodes
- For each storage node, there is a main disk with the type and size you specify; this disk is used to store chunks.
- For each storage node for an
SSDornon-replicated SSD, there is a service disk of the same type; this disk is used to store the logs and snapshots of dynamic tables. - The service disk size depends on the storage configuration and is calculated as follows:
- Assuming the storage node is for an
SSDwithNsize, the service disk size is0,1 × NGB, rounded up to the nearest integer. - Assuming the storage node is for a
non-replicated SSDwithNsize, the service disk size is0,1 × N, rounded up in increments of 93 GB.
- Assuming the storage node is for an
The price covers one month of use based on 720 hours per month. The minimum billing unit is 1 GB per minute (for example, storing 1 GB for 90 seconds counts as storing 1 GB for 2 minutes).
Example of cluster cost calculation
Let's calculate the cost of using a cluster with the following properties for 30 days:
Configurable components:
- Exec node: One
c8-m32configuration instance: 8 vCPUs and 32 GB RAM. - Tablet node: Three
c8-m16configuration instances, 8 vCPUs and 16 GB RAM. - Storage with the following configuration:
HDDstorage: Three disks, 2048 GB each.Non-replicated SSDstorage: Three disks, 465 GB each.
Service components:
-
Master node: Three configuration instances, 4 vCPUs and 12 GB RAM.
-
System node: Two configuration instances, 24 vCPUs and 64 GB RAM.
-
Proxy node: Two instances: One HTTP proxy and one RPC proxy, both with 4 vCPUs and 8 GB RAM.
-
Service tablet node: Two
c8-m16configuration instances, 8 vCPUs and 16 GB RAM. -
Storage with the following configuration:
-
Exec node storage: One non-replicated SSD, 93 GB.
-
Storage for service storage nodes: Three non-replicated SSDs, 93 GB each.
-
Storage for storage nodes: Six non-replicated SSDs, 93 GB each.
More info on service disks for storage nodes
- For three storage nodes for three non-replicated SSDs, 93 GB each, there will be three service disks, also non-replicated SSDs, 93 GB each.
- For three storage nodes for three non-replicated SSDs, 465 GB each, there will be three service disks, also non-replicated SSDs, 93 GB each.
-
-
Storage node: Six storage nodes, each with 8 vCPUs and 8 GB RAM; or three storage nodes, each with 4 vCPUs and 8 GB RAM.
More info on storage nodes
- For a storage with three non-replicated SSDs, 93 GB each, there are three service storage nodes, each with 8 vCPUs and 8 GB RAM.
- For a storage with three HDDs, 2048 GB each, there are three storage nodes, each with 4 vCPUs and 8 GB RAM.
- For a storage with three non-replicated SSDs, 465 GB each, there are three storage nodes, each with 8 vCPUs and 8 GB RAM.
Configurable components
Cost calculation for an exec node:
8 × $0.011342 + 32 × $0.003025 = $0.187536
Total: $0.187536, per hour cost of an exec node.
Where:
- 8: Number of vCPUs of one exec node.
- $0.011342: Cost per vCPU per hour.
- 32: Amount of RAM (GB) of one exec node.
- $0.003025: Cost of using 1 GB of RAM per hour.
Cost calculation for a tablet node:
3 × (8 × $0.011342 + 16 × $0.003025) = $0.417408
Total: $0.417408, per hour cost of tablet nodes.
Where:
- 3: Number of tablet nodes.
- 8: Number of vCPUs of one tablet node.
- $0.011342: Cost per vCPU per hour.
- 16: Amount of RAM (GB) of one tablet node.
- $0.003025: Cost of using 1 GB of RAM per hour.
Calculating the cost of cluster storage:
3 × 2,048 × $0.031533 + 3 × 465 × $0.095041 = $326.320947
Total: $326.320947, cost of using non-replicated SSD and network HDD storage per month.
Where:
- 3: Number of HDDs.
- 2,048: Size of one HDD (in GB).
- $0.031533: Cost of using one GB of network HDD storage per month.
- 3: Number of non-replicated SSDs.
- 465: Size of one non-replicated SSD (in GB).
- $0.095041: Cost of using one GB of non-replicated SSD storage per month.
Service components
Cost calculation for a master node:
3 × (4 × $0.011342 + 12 × $0.003025) = $0.245004
Total: $0.245004, per hour cost of master nodes.
Where:
- 3: Number of master nodes.
- 4: Number of vCPUs of one master node.
- $0.011342: Cost per vCPU per hour.
- 12: Amount of RAM (GB) of one master node.
- $0.003025: Cost of using 1 GB of RAM per hour.
Cost calculation for a system node:
2 × (24 × $0.011342 + 64 × $0.003025) = $0.931616
Total: $0.931616, per hour cost of system nodes.
Where:
- 2: Number of system nodes.
- 24: Number of vCPUs of one system node.
- $0.011342: Cost per vCPU per hour.
- 64: Amount of RAM (GB) of one system node.
- $0.003025: Cost of using 1 GB of RAM per hour.
Cost calculation for a proxy node:
2 × (4 × $0.011342 + 8 × $0.003025) = $0.139136
Total: $0.139136, per hour cost of proxy nodes.
Where:
- 2: Number of proxy nodes.
- 4: Number of vCPUs of one proxy node.
- $0.011342: Cost per vCPU per hour.
- 8: Amount of RAM (GB) of one proxy node.
- $0.003025: Cost of using 1 GB of RAM per hour.
Cost calculation for a service tablet node:
2 × (8 × $0.011342 + 16 × $0.003025) = $0.278272
Total: $0.278272, per hour cost of service tablet nodes.
Where:
- 2: Number of tablet nodes.
- 8: Number of vCPUs of one tablet node.
- $0.011342: Cost per vCPU per hour.
- 16: Amount of RAM (GB) of one tablet node.
- $0.003025: Cost of using 1 GB of RAM per hour.
Cost calculation for the exec node storage:
93 × 1 × $0.095041 = $8.838813
Total: $8.838813, cost of using non-replicated SSD storage for the exec node per month.
Where:
- 93: Size of non-replicated SSD storage (in GB).
- 1: Number of non-replicated SSDs.
- $0.095041: Cost of using one GB of non-replicated SSD storage per month.
Cost calculation for the service storage node storage:
3 × 93 × $0.095041 = $26.516439
Total: $26.516439, cost of using non-replicated SSD storage for the service storage nodes per month.
Where:
- 3: Number of disks.
- 93: Size of one non-replicated SSD (in GB).
- $0.095041: Cost of using one GB of non-replicated SSD storage per month.
Cost calculation for a storage node:
6 × (8 × $0.011342 + 8 × $0.003025) + 3 × (4 × $0.011342 + 8 × $0.003025) = $0.898320
Total: $0.898320, per hour cost of storage nodes.
Where:
- 6: Number of storage nodes for SSDs or non-replicated SSDs.
- 3: Number of storage nodes for HDDs.
- 8: Number of vCPUs per storage node for SSDs or non-replicated SSDs.
- 4: Number of vCPUs per storage node for HDDs.
- $0.011342: Cost per vCPU per hour.
- 8: Amount of RAM (GB) per storage node for SSDs or non-replicated SSDs.
- $0.003025: Cost of using 1 GB of RAM per hour.
Cost calculation for storage with service disks:
93 × 6 × $0.095041 = $53.032878
Total: $53.032878, cost of using non-replicated SSD storage per month.
Where:
- 6: Number of service disks.
- 93: Size of one non-replicated SSD (in GB).
- $0.095041: Cost of using one GB of non-replicated SSD storage per month.
Total cost calculation
720 × ($0.187536 + $0.417408 + $0.245004 + $0.931616 + $0.139136 + $0.278272 + $0.898320) + $326.320947 + $8.838813 + $26.516439 + $53.032878 = $2,644.759317
Total: $2,644.759317, cost of using the cluster for 30 days.
Where:
- 720: Hours in 30 days.
- $0.187536: Per hour cost of an exec node.
- $0.417408: Per hour cost of tablet nodes.
- $0.245004: Per hour cost of master nodes.
- $0.931616: Per hour cost of system nodes.
- $0.139136: Per hour cost of proxy nodes.
- $0.278272: Per hour cost of service tablet nodes.
- $0.898320: Per hour cost of storage nodes.
- $326.320947: Cost of using non-replicated SSD and network HDD storage per month.
- $8.838813: Cost of using non-replicated SSD storage for the exec node per month.
- $26.516439: Cost of using non-replicated SSD storage for the service storage nodes per month.
- $53.032878: Cost of using non-replicated SSD storage per month.
Prices for the Russia region
Note
Yandex Cloud resources are priced differently in different regions. For more information about the available regions, see Regions.
Your payment currency is determined by your contracting legal entity. For more information on creating an account, see Registering an account in Yandex Cloud.
The monthly usage rate is based on 720 hours a month.
Component computing resources
| Resource | Rate for 1 hour, without VAT |
Rate for 1 month, without VAT |
|---|---|---|
| Compute Node (Intel Ice Lake) | ||
| 100% vCPU | $0.011342 | $8.165997 |
| RAM (for 1 GB) | $0.003025 | $2.177999 |
| Compute Node (AMD Epyc with Nvidia A100) | ||
| 100% vCPU | $0.009720 | $6.998397 |
| RAM (for 1 GB) | $0.003024 | $2.177399 |
| 1 GPU Nvidia A100 | $4.014415 | $2890.378844 |
| Compute Node (Intel Cascade Lake with Nvidia Tesla V100) | ||
| 100% vCPU | $0.012275 | $8.837996 |
| RAM (for 1 GB) | $0.003193 | $2.299199 |
| 1 GPU Nvidia Tesla V100 | $2.570082 | $1850.459260 |
| Compute Node (Intel Ice Lake with T4i) | ||
| 100% vCPU | $0.011340 | $8.164796 |
| RAM (for 1 GB) | $0.003024 | $2.177399 |
| 1 GPU | $1.555166 | $1119.719552 |
| Master Node (Intel Ice Lake) | ||
| 100% vCPU | $0.011342 | $8.165997 |
| RAM (for 1 GB) | $0.003025 | $2.177999 |
| Proxy Node (Intel Ice Lake) | ||
| 100% vCPU | $0.011342 | $8.165997 |
| RAM (for 1 GB) | $0.003025 | $2.177999 |
| Storage Node (Intel Ice Lake) | ||
| 100% vCPU | $0.011342 | $8.165997 |
| RAM (for 1 GB) | $0.003025 | 720 × $0.003025 |
| System Node (Intel Ice Lake) | ||
| 100% vCPU | $0.011342 | $8.165997 |
| RAM (for 1 GB) | $0.003025 | $2.177999 |
| Tablet Node (Intel Ice Lake) | ||
| 100% vCPU | $0.011342 | $8.165997 |
| RAM (for 1 GB) | $0.003025 | $2.177999 |
Storage
| Resource | Price of 1 GB per month, without VAT |
|---|---|
| Network HDD storage | $0.031533 |
| Non-replicated SSD storage | $0.095041 |
| Network SSD storage | $0.128625 |
Outbound traffic
When using the service, you pay for traffic from Yandex Cloud to the internet. Traffic between internal IP addresses of Yandex Cloud services and incoming internet traffic is free.
The first 100 GB of outgoing traffic per month are free of charge.
The minimum billing unit is 1 MB.
| Resource category | Price of 1 GB, without VAT |
|---|---|
| Outgoing traffic, 100 GB or less per month | Free |
| Outgoing traffic, over 100 GB per month | $0.013770 |