manual added knowledge_base
16
collections/manual/knowledge_base/cloud/cloud_toc.md
Normal file
@@ -0,0 +1,16 @@
|
||||
<h1> Cloud </h1>
|
||||
|
||||
This section covers the essential information concerning Cloud utilization.
|
||||
|
||||
To deploy on the ThreeFold Grid, refer to the [System Administrators](../../documentation/system_administrators/system_administrators.md) section.
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Cloud Units](./cloudunits.md)
|
||||
- [Pricing](./pricing/pricing_toc.md)
|
||||
- [Pricing Overview](./pricing/pricing.md)
|
||||
- [Staking Discounts](./pricing/staking_discount_levels.md)
|
||||
- [Cloud Pricing Compare](./pricing/cloud_pricing_compare.md)
|
||||
- [Grid Billing](./grid_billing/grid_billing.md)
|
||||
- [Resource Units](./resource_units_calc_cloudunits.md)
|
||||
- [Resource Units Advanced](./resourceunits_advanced.md)
|
69
collections/manual/knowledge_base/cloud/cloudunits.md
Normal file
@@ -0,0 +1,69 @@
|
||||
<h1>Cloud Units</h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [What are Cloud Units?](#what-are-cloud-units)
|
||||
- [How is the price of Cloud Units (v4) calculated?](#how-is-the-price-of-cloud-units-v4-calculated)
|
||||
- [Compute Capacity](#compute-capacity)
|
||||
- [Storage Capacity](#storage-capacity)
|
||||
- [Network](#network)
|
||||
|
||||
***
|
||||
|
||||
## What are Cloud Units?
|
||||
Cloud units are the basis for price calculation for anyone intending to use/deploy on the Threefold Grid.
|
||||
|
||||
Cloud units are a unified way to account for virtual hardware resources on the ThreeFold Grid. They represent compute, storage and network equivalents to energy (kW - kilowatt). The are three categories of cloud units:
|
||||
|
||||
- Compute Unit (CU): The amount of data processing power in terms of virtual CPU (vCPU) cores (logical [CPUs](https://en.wikipedia.org/wiki/Central_processing_unit)) and Random Access Momory ([RAM](https://en.wikipedia.org/wiki/Random-access_memory)).
|
||||
- Storage Unit (SU): The amount of storage capacity in terms of Hard Disk Drives (HDDs) and Solid State Drives (SSDs) in Gigabytes (GB).
|
||||
- Network Unit (NU): The amount of data that travels in and out of storage units or compute units expressed in GB.
|
||||
|
||||
> Note: [Resource units](./resource_units_calc_cloudunits.md) are used to calculate SU & CU. Resource Units are used to measure compute and storage capacity produced by hardware.
|
||||
|
||||
When a solution is deployed on the ThreeFold Grid, the system automatically gathers the required amount of CU, SU, or NU. It is important to note that users are not billed upon reservation but only when utilizing the actualy CU, SU and NU. TF Certified Farmers can define the price of CU, SU, and NU they make available on the ThreeFold Grid.
|
||||
|
||||
## How is the price of Cloud Units (v4) calculated?
|
||||
|
||||
The following tables display how cloud units (v4) are calculated on the ThreeFold Grid. The 4th version of cloud units are used since Grid 2.2+ in mid 2020.
|
||||
|
||||
### Compute Capacity
|
||||
|
||||
| CU (Compute Unit) | | | | |
|
||||
| ------------------------------------- | --- | --- | ---- | --------------- |
|
||||
| GB Memory | 4 | 8 | 2 | |
|
||||
| nr vCPU | 2 | 1 | 4 | |
|
||||
| Passmark Minimum (expected is double) | 500 | 250 | 1000 | CPU performance |
|
||||
|
||||
The passmark (CPU benchmark or alternative) is not measured on the grid yet. It is used in simulators to check the mechanisms and ensure enough performance per CU is delivered.
|
||||
|
||||
Example of Compute unit:
|
||||
- 4 GB memory & 2 virtual CPU (and 50GB of SSD disk space)
|
||||
- Recommended price on TF Grid = 10 USD
|
||||
- Alternative cloud price = between 40 USD and 180 USD
|
||||
|
||||
See how we compare with the market compute prices [here](./pricing/pricing.md).
|
||||
|
||||
### Storage Capacity
|
||||
|
||||
| SU (Storage Unit) | HDD | SSD |
|
||||
| ------------------- | ---- | --- |
|
||||
| GB Storage Capacity | 1200 | 200 |
|
||||
|
||||
HDD is only usable for Zero Database driven storage (e.g. ThreeFold Quantum Safe Storage). 1.2 TB of HDD is provided following the advised storage policy of 16+4 with 20% overhead. So the net usable storage would be 1TB. In other words, the SU corresponds in that case to 1TB of net usable storage and an extra 200GB for redundancy.
|
||||
|
||||
Example of Storage unit:
|
||||
|
||||
- 1TB of usable storage as provided by the Zero-DBs (the backend storage systems)
|
||||
- Recommended price on TF Grid for 1 SU = 10 USD
|
||||
- Alternative cloud price = between 20 USD and 200 USD
|
||||
|
||||
See how we compare with market storage prices [here](./pricing/pricing.md).
|
||||
|
||||
### Network
|
||||
|
||||
| NU (Network Unit = per GB) = NRU per month | GB (NRU) |
|
||||
| ------------------------------------------ | -------- |
|
||||
| GB transferred OUT or IN | 1 |
|
||||
|
||||
> We use SU-month and CU-month to show SU monthly costs. This can be compared to kilowatts (kW) to see electricity usage per month. Learn more about how this is calculated with [Resource units](./resource_units_calc_cloudunits.md), a way to measure the compute and storage capacity produced by hardware.
|
@@ -0,0 +1,52 @@
|
||||
# Cloud Units Advanced
|
||||
|
||||
## How is the price of Cloud Units (v4) calculated?
|
||||
|
||||
The following tables display how cloud units (v4) are calculated on the ThreeFold Grid. The 4th version of cloud units are used since Grid 2.2+ in mid 2020.
|
||||
|
||||
> Note: [Resource units](resource_units.md) are used to calculate SU & CU. Resource Units are used to measure compute and storage capacity produced by hardware.
|
||||
|
||||
### Compute Capacity
|
||||
|
||||
| CU (Compute Unit) | | | | |
|
||||
| ------------------------------------- | --- | --- | ---- | --------------- |
|
||||
| GB Memory | 4 | 8 | 2 | |
|
||||
| nr vCPU | 2 | 1 | 4 | |
|
||||
| Passmark Minimum (expected is double) | 500 | 250 | 1000 | CPU performance |
|
||||
|
||||
The passmark (CPU benchmark or alternative) is not measured on the grid yet. It is used in simulators to check the mechanisms and ensure enough performance per CU is delivered.
|
||||
|
||||
Example of Compute unit:
|
||||
|
||||
- 4 GB memory & 2 virtual CPU (and 50GB of SSD disk space)
|
||||
- Recommended price on TF Grid = 10 USD
|
||||
- Alternative cloud price = between 40 USD and 180 USD
|
||||
|
||||
See how we compare with the market compute prices [here](pricing).
|
||||
|
||||
### Storage Capacity
|
||||
|
||||
| SU (Storage Unit) | HDD | SSD |
|
||||
| ------------------- | ---- | --- |
|
||||
| GB Storage Capacity | 1200 | 200 |
|
||||
|
||||
HDD is only usable for Zero Database driven storage (e.g. ThreeFold Quantum Safe Storage). 1.2 TB of HDD is provided following the advised storage policy of 16+4 with 20% overhead. So the net usable storage would be 1TB. In other words, the SU corresponds in that case to 1TB of net usable storage and an extra 200GB for redundancy.
|
||||
|
||||
Example of Storage unit:
|
||||
|
||||
- 1TB of usable storage as provided by the Zero-DBs (the backend storage systems)
|
||||
- Recommended price on TF Grid for 1 SU = 10 USD
|
||||
- Alternative cloud price = between 20 USD and 200 USD
|
||||
|
||||
See how we compare with market storage prices [here](pricing).
|
||||
|
||||
### Network
|
||||
|
||||
| NU (Network Unit = per GB) = NRU per month | GB (NRU) |
|
||||
| ------------------------------------------ | -------- |
|
||||
| GB transferred OUT or IN | 1 |
|
||||
|
||||
> We use SU-month and CU-month to show SU monthly costs. This can be compared to kilowatts (kW) to see electricity usage per month. Learn more about how this is calculated with [Resource units](resource_units), a way to measure the compute and storage capacity produced by hardware.
|
||||
|
||||
|
||||
|
@@ -0,0 +1,422 @@
|
||||
<h1>Grid Billing</h2>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Resources to Update](#resources-to-update)
|
||||
- [Current TFT Price](#current-tft-price)
|
||||
- [Current Cloud Units Values](#current-cloud-units-values)
|
||||
- [Node Contract](#node-contract)
|
||||
- [Calculating the CU](#calculating-the-cu)
|
||||
- [Calculating the SU](#calculating-the-su)
|
||||
- [Calculating the Billing Rate for the Contract](#calculating-the-billing-rate-for-the-contract)
|
||||
- [Applying the Discounts](#applying-the-discounts)
|
||||
- [Rent Contract](#rent-contract)
|
||||
- [Getting the Resources](#getting-the-resources)
|
||||
- [Calculating the CU](#calculating-the-cu-1)
|
||||
- [Calculating the SU](#calculating-the-su-1)
|
||||
- [Calculating the Billing Rate for the Contract](#calculating-the-billing-rate-for-the-contract-1)
|
||||
- [Applying the Dedicated Node Discount](#applying-the-dedicated-node-discount)
|
||||
- [Applying the Staking Discount](#applying-the-staking-discount)
|
||||
- [Name Contract](#name-contract)
|
||||
- [Applying the Staking Discount](#applying-the-staking-discount-1)
|
||||
- [Public IP](#public-ip)
|
||||
- [Applying the Staking Discount](#applying-the-staking-discount-2)
|
||||
- [Network Usage](#network-usage)
|
||||
- [Data Usage](#data-usage)
|
||||
- [NU Value](#nu-value)
|
||||
- [Applying the Staking Discount](#applying-the-staking-discount-3)
|
||||
- [Billing History](#billing-history)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
In this section, we explain how the billing works on the TFGrid by showing different examples such as node, rent and name contracts as well as public IP and network usage.
|
||||
|
||||
<!--
|
||||
|
||||
(We can add this when 3.13 is released)
|
||||
|
||||
This documentation can be used in parallel with the [TFGrid Pricing Calculator](https://dashboard.grid.tf/#/deploy/pricing-calculator/) available on the Dashboard.
|
||||
|
||||
-->
|
||||
|
||||
## Resources to Update
|
||||
|
||||
Some of the used resources should be updated whenever you try to do these calculations, these resources are the TFT price and the cloud units (SU and CU).
|
||||
|
||||
### Current TFT Price
|
||||
|
||||
TFT price can be retrieved directly through [Stellar](https://stellar.expert/explorer/public/asset/TFT-GBOVQKJYHXRR3DX6NOX2RRYFRCUMSADGDESTDNBDS6CDVLGVESRTAC47-1?asset[]=TFT-GBOVQKJYHXRR3DX6NOX2RRYFRCUMSADGDESTDNBDS6CDVLGVESRTAC47-1&filter=markets&market=USDC-GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN-1) or from the [Dashboard](https://dashboard.grid.tf/), through the price available in the header.
|
||||
|
||||

|
||||
|
||||
### Current Cloud Units Values
|
||||
|
||||
The current cloud units values can be retrieved directly from TChain with the [Polkadot UI](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftfchain.grid.tf#/chainstate) and the current chain state.
|
||||
|
||||
- On the page `Chain State`, select `tfgridModule` as the `selected state query`
|
||||
- Select `pricingPolicies(u32): Option<PalletTfgridPricingPolicy>`
|
||||
- Enter the value of the default pricing policy, which is `1`, or enter the value of any other policy if you need to use a custom one
|
||||
- Press `Enter`
|
||||
|
||||

|
||||
|
||||
> Note: Values on chain are expressed as "units USD per hour", where "1 unit USD" == 10.000.000 (or 1e7)
|
||||
|
||||
## Node Contract
|
||||
|
||||
For this example, we will assume that the resources for this deployment are the following:
|
||||
|
||||
```
|
||||
CRU: 2
|
||||
MRU: 2
|
||||
SRU: 15
|
||||
HRU: 0
|
||||
```
|
||||
|
||||
### Calculating the CU
|
||||
|
||||
Let's calculate the CU of this deployment.
|
||||
|
||||
For our example, the CU value is `10 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||
|
||||
```
|
||||
CU = min( max(MRU/4, CRU/2), max(MRU/8, CRU), max(MRU/2, CRU/4) )
|
||||
= min( max(2/4, 2/2), max(2/8, 2), max(2/2, 2/4) )
|
||||
= min( max(0.5, 1), max(0.25, 2), max(1, 0.5) )
|
||||
= min( 1, 2, 1 )
|
||||
= 1
|
||||
CU cost/hour = CU * CU pricing
|
||||
= 1 * 10 mUSD/h
|
||||
= 10 mUSD/h
|
||||
```
|
||||
|
||||
|
||||
### Calculating the SU
|
||||
|
||||
Let's calculate the SU of this deployment.
|
||||
|
||||
The current SU value is `5 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||
|
||||
```
|
||||
SU = HRU/1200 + SRU/200
|
||||
= 0/1200 + 15/200
|
||||
= 0 + 0.075
|
||||
= 0.075
|
||||
SU cost/hour = SU * SU pricing
|
||||
= 0.075 * 5 mUSD/h
|
||||
= 0.375 mUSD/h
|
||||
```
|
||||
|
||||
|
||||
### Calculating the Billing Rate for the Contract
|
||||
|
||||
Let's calculate the billing rate by combining the CU and SU from above.
|
||||
|
||||
For this example, the current TFT value is `0.011 USD`. Make sure that this value is updated according to the current TFT value.
|
||||
|
||||
```
|
||||
Contract cost/hour = CU cost/hour + SU cost/hour
|
||||
= 10 mUSD/h + 0.375 mUSD/h
|
||||
= 10.375 mUSD/h
|
||||
= 0.010375 USD/h
|
||||
= 0.010375 * 24 * 30
|
||||
= 7.47 USD/month
|
||||
= 679.090909 TFT/month
|
||||
= 0.943182 TFT/hour
|
||||
```
|
||||
|
||||
### Applying the Discounts
|
||||
|
||||
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||
|
||||
For this example, we assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||
|
||||
The 60% discount is thus equivalent to paying only 40% of the total price, as shown below:
|
||||
|
||||
```
|
||||
Cost with 60% discount = 0.943182 * 0.4
|
||||
= 0.377273 TFT/hour
|
||||
```
|
||||
|
||||
|
||||
## Rent Contract
|
||||
|
||||
|
||||
### Getting the Resources
|
||||
|
||||
You can get the resources of a node using different methods. You can use Grid Proxy, GraphQL and the Polkadot UI.
|
||||
|
||||
- Using Grid Proxy
|
||||
- Grid Proxy API
|
||||
- Go to the section [nodes endpoint](https://gridproxy.grid.tf/swagger/index.html#/GridProxy/get_nodes__node_id_)
|
||||
- Click on `Try it out`
|
||||
- Write the node ID
|
||||
- Click on `Execute`
|
||||
- Grid Proxy URL
|
||||
- You can use the following URL and replace <node_id> by the node ID:
|
||||
```
|
||||
https://gridproxy.grid.tf/nodes/<node_id>
|
||||
```
|
||||
|
||||
- Using GraphQL
|
||||
|
||||
Navigate to [ThreeFold's GraphQL](https://graphql.grid.tf/graphql), then use the following query and replace the node id with the desired node id.
|
||||
|
||||
```
|
||||
query MyQuery {
|
||||
nodes(where: {nodeID_eq: 83}) {
|
||||
id
|
||||
farmingPolicyId
|
||||
resourcesTotal {
|
||||
cru
|
||||
mru
|
||||
sru
|
||||
hru
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
```
|
||||
|
||||
- TFChain and Polkadot UI
|
||||
- On the page Chain State of the [polakdot UI](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Ftfchain.grid.tf#/chainstate), select `tfgridModule` as the `selected state query`
|
||||
- Select `nodes(u32): Option<TfchainSupportNode>`
|
||||
- Enter the node ID
|
||||
- Press `Enter`
|
||||
|
||||

|
||||
|
||||
|
||||
For our example, these are the resources for node `83` that will be used for the calculations.
|
||||
|
||||
```
|
||||
CRU = 4
|
||||
SRU = 119.24
|
||||
HRU = 1863
|
||||
MRU = 15.55
|
||||
```
|
||||
|
||||
### Calculating the CU
|
||||
|
||||
Let's calculate the CU of this deployment.
|
||||
|
||||
For our example, the CU value is `10 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||
|
||||
```
|
||||
CU = min( max(MRU/4, CRU/2), max(MRU/8, CRU), max(MRU/2, CRU/4) )
|
||||
= min( max(15.55/4, 4/2), max(15.55/8, 4), max(15.55/2, 4/4) )
|
||||
= min( max(3.8875, 2), max(1.94375, 4), max(7.775, 1) )
|
||||
= min( 3.8875, 4, 7.775 )
|
||||
= 3.8875
|
||||
CU cost/hour = CU * CU pricing
|
||||
= 3.8875 * 10 mUSD/h
|
||||
= 38.875 mUSD/h
|
||||
```
|
||||
|
||||
|
||||
### Calculating the SU
|
||||
|
||||
For our example, the SU value is `5 mUSD/h`. Make sure that this value is updated according to the current values.
|
||||
|
||||
```
|
||||
SU = HRU/1200 + SRU/200
|
||||
= 1863/1200 + 119.24/200
|
||||
= 1.5525 + 0.5962
|
||||
= 2.1487
|
||||
SU cost/hour = SU * SU pricing
|
||||
= 2.1487 * 5 mUSD/h
|
||||
= 10.7435 mUSD/h
|
||||
```
|
||||
|
||||
### Calculating the Billing Rate for the Contract
|
||||
|
||||
For our example, the current TFT value is `0.011 USD`. Make sure that this value is updated according to the current values.
|
||||
|
||||
```
|
||||
Contract cost/hour = CU cost/hour + SU cost/hour
|
||||
= 38.875 mUSD/h + 10.7435 mUSD/h
|
||||
= 49.6185 mUSD/h
|
||||
= 0.0496185 USD/h
|
||||
= (0.0496185 * 24 * 30)
|
||||
= 35.72532 USD/month
|
||||
= 3247.75636 TFT/month
|
||||
```
|
||||
|
||||
### Applying the Dedicated Node Discount
|
||||
|
||||
There's a default `50%` discount for renting a node, this discount is not related to the staking discount. For more information on dedicated node discounts, please [read this section](../../../documentation/dashboard/deploy/dedicated_machines.md).
|
||||
|
||||
```
|
||||
Cost with 50% discount = 35.72532 * 0.5
|
||||
= 17.86266 TFT/month
|
||||
```
|
||||
|
||||
### Applying the Staking Discount
|
||||
|
||||
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||
|
||||
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||
|
||||
|
||||
|
||||
```
|
||||
Cost with 60% discount = 17.86266 * 0.4
|
||||
= 7.145064 TFT/month
|
||||
```
|
||||
|
||||
## Name Contract
|
||||
|
||||
Let's calculate the cost of a name contract.
|
||||
|
||||
For our example, we use the following value from the Pricing Policy.
|
||||
|
||||

|
||||
|
||||
This value can then be converted to USD.
|
||||
|
||||
```
|
||||
uniqueName in USD = 2500 / 10000000
|
||||
= 0.00025 USD/hour
|
||||
|
||||
```
|
||||
Since the current TFT conversion rate is `1 USD = 100 TFT`, we have the following:
|
||||
|
||||
```
|
||||
uniqueName in TFT = 0.00025 * 100
|
||||
= 0.025 TFT/hour
|
||||
```
|
||||
|
||||
### Applying the Staking Discount
|
||||
|
||||
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||
|
||||
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||
|
||||
```
|
||||
Cost with 60% discount = 0.025 * 0.4
|
||||
= 0.01 TFT/hour
|
||||
|
||||
```
|
||||
|
||||
## Public IP
|
||||
|
||||
Let's calculate the cost of public IPs.
|
||||
|
||||
For our example, we use the following value from the Pricing Policy.
|
||||
|
||||

|
||||
|
||||
This value can then be converted to USD.
|
||||
|
||||
```
|
||||
Public IP in USD = 40000 / 10000000
|
||||
= 0.004 USD/hour
|
||||
|
||||
```
|
||||
|
||||
Since the current TFT conversion rate is `1 USD = 100 TFT`, we have the following:
|
||||
|
||||
```
|
||||
Public IP in TFT = 0.004 * 100
|
||||
= 0.4 TFT/hour
|
||||
```
|
||||
|
||||
### Applying the Staking Discount
|
||||
|
||||
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||
|
||||
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||
|
||||
```
|
||||
Cost with 60% discount = 0.4 * 0.4
|
||||
= 0.16 TFT/hour
|
||||
|
||||
```
|
||||
|
||||
> Note: This value gets added to the billing rate of your deployment.
|
||||
|
||||
|
||||
## Network Usage
|
||||
|
||||
Network Usage is calculated for deployments with public IPs. It's reported every hour and its cost can be calculated approximately as follows, where the data usage is the value of data sent and received:
|
||||
|
||||
```
|
||||
network usage = data usage * NU value
|
||||
```
|
||||
|
||||
### Data Usage
|
||||
|
||||
To start, let's calculate the data usage. This can be tracked with a network tool like [nload](https://github.com/rolandriegel/nload), where the total amount of data sent and received can be displayed.
|
||||
|
||||

|
||||
|
||||
|
||||
### NU Value
|
||||
|
||||
Let's find the NU value of this deployment.
|
||||
|
||||
For our example, we use the following value from the Pricing Policy.
|
||||
|
||||

|
||||
|
||||
This value can then be converted to USD.
|
||||
|
||||
```
|
||||
NU price in USD = 15000 / 10000000
|
||||
= 0.0015 USD/hour
|
||||
|
||||
```
|
||||
Since in our example the current TFT conversion rate is `1 USD = 100 TFT`, we have the following:
|
||||
|
||||
```
|
||||
NU price in TFT = 0.0015 * 100
|
||||
= 0.15 TFT/hour
|
||||
```
|
||||
|
||||
### Applying the Staking Discount
|
||||
|
||||
Before assuming that the price above is the final price, check first if your twin is eligible for any of the available staking discount levels. To understand more about discount levels, please read [this section](../pricing/staking_discount_levels.md).
|
||||
|
||||
For this example, let's assume that this twin has 18 months worth of TFTs staked, so the user will be eligible for a Gold discount level (60% discount).
|
||||
|
||||
```
|
||||
Cost with 60% discount = 0.15 * 0.4
|
||||
= 0.06 TFT/hour
|
||||
|
||||
```
|
||||
|
||||
As an example, let's assume that we used a total of 10GB in the last hour, so the next hour the billing rate should be updated to:
|
||||
|
||||
```
|
||||
Total network usage = 10GB * 0.06 TFT/hour
|
||||
= 0.6 TFT/hour
|
||||
```
|
||||
|
||||
The billing rate in the next hour should be the following:
|
||||
|
||||
```
|
||||
hourly billing rate = actual cost of the deployment + total network usage
|
||||
```
|
||||
|
||||
|
||||
> Note: The calculated value will always be an approximation since it's not possible to manually calculate the exact value of the data used.
|
||||
|
||||
|
||||
## Billing History
|
||||
|
||||
Since the billing rate gets updated hourly, you can check the billing history from [GraphQL](https://graphql.grid.tf/graphql) using the following query. Make sure to enter the proper contract ID.
|
||||
|
||||
```
|
||||
query MyQuery {
|
||||
contractBillReports(where: {contractID_eq: ""}) {
|
||||
contractID
|
||||
amountBilled
|
||||
discountReceived
|
||||
timestamp
|
||||
}
|
||||
}
|
||||
|
||||
```
|
After Width: | Height: | Size: 25 KiB |
After Width: | Height: | Size: 105 KiB |
After Width: | Height: | Size: 98 KiB |
After Width: | Height: | Size: 91 KiB |
After Width: | Height: | Size: 78 KiB |
After Width: | Height: | Size: 42 KiB |
After Width: | Height: | Size: 78 KiB |
After Width: | Height: | Size: 315 KiB |
@@ -0,0 +1,55 @@
|
||||
<h1>Price comparison Cloudorado</h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Compute](#compute)
|
||||
- [Compute Conclusion](#compute-conclusion)
|
||||
- [Storage](#storage)
|
||||
- [Storage Conclusion](#storage-conclusion)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
We compare cloud pricing with Cloudorado. Note that the information here can be subject to change and might not reflect current market prices.
|
||||
|
||||
## Compute
|
||||
|
||||
A ThreeFold Compute Unit is (CU)
|
||||
|
||||
- 4 GB memory
|
||||
- 2 virtual CPU cores
|
||||
|
||||
A good site to compare is Cloudorado: https://www.cloudorado.com/
|
||||
|
||||

|
||||
|
||||
| Compute | Compute |
|
||||
| --------------------------------- | --------------------------------- |
|
||||
|  |  |
|
||||
|
||||
|
||||
### Compute Conclusion
|
||||
|
||||
> Our price can easily be < 10 USD for 1 compute unit (CU) <BR>
|
||||
> In market, this is between 36 and 202 USD
|
||||
|
||||
## Storage
|
||||
|
||||
A ThreeFold Storage Unit is (SU)
|
||||
|
||||
- 1 TB of storage
|
||||
|
||||
Again, a good site to compare is Cloudorado: https://www.cloudorado.com/
|
||||
|
||||

|
||||
|
||||

|
||||
|
||||
### Storage Conclusion
|
||||
|
||||
> Our price can easily be < 8 USD for 1 storage unit (CU) <BR>
|
||||
> In market, this is between 19 and 154 USD
|
||||
|
||||
<!-- TODO: Update with current market and add generated_on -->
|
@@ -0,0 +1,69 @@
|
||||
|
||||

|
||||
|
||||
## Cloud Unit Pricing
|
||||
|
||||
| Cloud Units | description | mUSD | mTFT |
|
||||
| ----------------- | ------------------------------------------------ | ------------------ | ------------------ |
|
||||
| Compute Unit (CU) | typically 2 vcpu, 4 GB mem, 50 GB storage | $CU_MUSD_HOUR/hour | $CU_MTFT_HOUR/hour |
|
||||
| Storage Unit (SU) | typically 1 TB of netto usable storage (*) | $SU_MUSD_HOUR/hour | $SU_MTFT_HOUR/hour |
|
||||
| Network Unit (NU) | 1 GB transfer, bandwidth as used by TFGrid users | $NU_MUSD_GB/GB | $NU_MTFT_GB/GB |
|
||||
|
||||
|
||||
| Network Addressing | description | mUSD | mTFT |
|
||||
| ------------------ | ------------------------------------------ | --------------------- | --------------------- |
|
||||
| IPv4 Address | Public Ip Address as used by a TFGrid user | $IP_MUSD_HOUR/hour | $IP_MTFT_HOUR/hour |
|
||||
| Unique Name | Usable as name on webgateways | $NAME_MUSD_HOUR/hour | $NAME_MTFT_HOUR/hour |
|
||||
| Unique Domain Name | Usable as dns name on webgateways | $DNAME_MUSD_HOUR/hour | $DNAME_MTFT_HOUR/hour |
|
||||
|
||||
- mUSD = 1/1000 of USD, mTFT = 1/1000 of TFT
|
||||
- TFT pricing pegged to USD (pricing changes in line with TFT/USD rate)
|
||||
- **current TFT to USD price is $TFTUSD** , calculated on $NOW
|
||||
- pricing is calculated per hour for the TFGrid 3.0
|
||||
<!-- - pricing of capacity of certified farmers is 25% more (x 1.25) (future development) -->
|
||||
|
||||
|
||||
### Pricing Expressed Per Month
|
||||
|
||||
| Cloud Units | description | USD NO DISCOUNT | USD 60% DISCOUNT |
|
||||
| ----------------- | ------------------------------------------------ | ------------------- | ---------------------------- |
|
||||
| Compute Unit (CU) | typically 2 vcpu, 4 GB mem, 50 GB storage | $CU_USD_MONTH/month | $CU_USD_MONTH_DISCOUNT/month |
|
||||
| Storage Unit (SU) | typically 1 TB of netto usable storage (*) | $SU_USD_MONTH/month | $SU_USD_MONTH_DISCOUNT/month |
|
||||
| Network Unit (NU) | 1 GB transfer, bandwidth as used by TFGrid users | $NU_USD_GB/GB | $NU_USD_MONTH_DISCOUNT/GB |
|
||||
| IPv4 Address | Public Ip Address as used by a TFGrid user | $IP_USD_MONTH/month | $IP_USD_MONTH_DISCOUNT/month |
|
||||
|
||||
|
||||
> Please check pricing calculator on http://pricing.threefold.me
|
||||
|
||||
### Dedicated Servers
|
||||
|
||||
Starting April 2022, the TFGrid 3.0/a5 has support for dedicated servers. You can reserve a full server and the server is only usable for you, a minimum of 70% discount is given for this usecase.
|
||||
|
||||
- Dedicated Node, 192 GB mem, 24 cores, 1000 GB SSD = 75 USD per month (max discount, 3Y staking)
|
||||
- Dedicated Node, 32 GB mem, 8 cores, 1000 GB SSD = 31 USD per month (max discount, 3Y staking)
|
||||
|
||||
Above example was with generous 5TB of bandwidth used per node per month, which is huge.
|
||||
|
||||
These nodes are ideal to deploy blockchain nodes, or other high demanding workloads. Dedicated nodes leads to amazing pricing.
|
||||
|
||||
To use a dedicated node, you will have to reserve a 3node for yourself in your admin portal of TFGrid, only you can then deploy on this node and there is no additional cost.
|
||||
|
||||
> Please check pricing calculator on http://pricing.threefold.me
|
||||
|
||||
|
||||
### How to buy and use capacity
|
||||
|
||||
- More info about [how to use the grid see here](grid_use)
|
||||
- See our manual how to get started.
|
||||
- [TFT's can be bought on multiple locations](how_to_buy).
|
||||
|
||||
### More Info
|
||||
|
||||
- See [here for more info about planet positive certification](certified_farming)
|
||||
- Pricing is done based on cloud units, see [cloudunits](cloudunits)
|
||||
|
||||
!!!include:staking_discount_levels
|
||||
|
||||
!!!def alias:tfpricing,cloudunit_pricing,threefold_pricing
|
||||
|
||||
!!!tfpriceinfo
|
After Width: | Height: | Size: 85 KiB |
After Width: | Height: | Size: 213 KiB |
After Width: | Height: | Size: 206 KiB |
After Width: | Height: | Size: 43 KiB |
After Width: | Height: | Size: 179 KiB |
After Width: | Height: | Size: 42 KiB |
After Width: | Height: | Size: 170 KiB |
98
collections/manual/knowledge_base/cloud/pricing/pricing.md
Normal file
@@ -0,0 +1,98 @@
|
||||
<h1> Cloud Unit Pricing </h1>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Pricing Policy](#pricing-policy)
|
||||
- [Pricing Expressed Per Month](#pricing-expressed-per-month)
|
||||
- [Operation Fees](#operation-fees)
|
||||
- [Certified Capacity](#certified-capacity)
|
||||
- [Dedicated Nodes](#dedicated-nodes)
|
||||
- [Staking Discount](#staking-discount)
|
||||
- [Example for 40% discount (Silver)](#example-for-40-discount-silver)
|
||||
|
||||
***
|
||||
|
||||
## Pricing Policy
|
||||
|
||||
- The current prices are for resources usage on mainnet (testnet get 50% discount)
|
||||
- A month is considered as 30 days (720 hours)
|
||||
|
||||
| Cloud Units | Description | mUSD | mTFT |
|
||||
| ----------------- | ------------------------------------------------ | ------------------ | ------------------ |
|
||||
| Compute Unit (CU) | typically 2 vcpu, 4 GB mem, 50 GB storage | {{#include ../../../values/CU_MUSD_HOUR.md}}/hour | {{#include ../../../values/CU_MTFT_HOUR.md}}/hour |
|
||||
| Storage Unit (SU) | typically 1 TB of netto usable storage (*) | {{#include ../../../values/SU_MUSD_HOUR.md}}/hour | {{#include ../../../values/SU_MTFT_HOUR.md}}/hour |
|
||||
| Network Unit (NU) | 1 GB transfer, bandwidth as used by TFGrid users | {{#include ../../../values/NU_MUSD_HOUR.md}}/hour | {{#include ../../../values/NU_MTFT_HOUR.md}}/hour |
|
||||
|
||||
<br>
|
||||
|
||||
| Network Addressing | Description | mUSD | mTFT |
|
||||
| ------------------ | ------------------------------------------ | --------------------- | --------------------- |
|
||||
| IPv4 Address | Public Ip Address as used by a TFGrid user | {{#include ../../../values/IP_MUSD_HOUR.md}}/hour | {{#include ../../../values/IP_MTFT_HOUR.md}}/hour |
|
||||
| Unique Name | Usable as name on webgateways | {{#include ../../../values/NAME_MUSD_HOUR.md}} | {{#include ../../../values/NAME_MTFT_HOUR.md}}/hour |
|
||||
| Unique Domain Name | Usable as dns name on webgateways | {{#include ../../../values/DNAME_MUSD_HOUR.md}}/hour | {{#include ../../../values/DNAME_MTFT_HOUR.md}}/hour |
|
||||
|
||||
- mUSD = 1/1000 of USD, mTFT = 1/1000 of TFT
|
||||
- TFT pricing pegged to USD (pricing changes in line with TFT/USD rate)
|
||||
- The current TFT to USD price is {{#include ../../../values/tft_value.md}} USD
|
||||
- pricing is calculated per hour for the TFGrid 3.0
|
||||
|
||||
> Please check our [Cloud Pricing for utilization sheet](https://docs.google.com/spreadsheets/d/1E6MpGs15h1_flyT5AtyKp1TixH1ILuGo5tzHdmjeYdQ/edit#gid=2014089775) for more details.
|
||||
|
||||
## Pricing Expressed Per Month
|
||||
|
||||
| Cloud Units | description | USD NO DISCOUNT | USD 60% DISCOUNT |
|
||||
| ----------------- | ------------------------------------------------ | ------------------- | ---------------------------- |
|
||||
| Compute Unit (CU) | typically 2 vcpu, 4 GB mem, 50 GB storage | 22.00/month | 8.80/month |
|
||||
| Storage Unit (SU) | typically 1 TB of netto usable storage | 14.00/month | 5.60/month |
|
||||
| Network Unit (NU) | 1 GB transfer, bandwidth as used by TFGrid users | 0.05/GB | 0.03/GB |
|
||||
| IPv4 Address | Public Ip Address as used by a TFGrid user | 5.00/month | 3.00/month |
|
||||
|
||||
## Operation Fees
|
||||
|
||||
Operations on TFChain have a base fee of 0.001 TFT. Creating and destroying deployments usually includes several operations.
|
||||
|
||||
## Certified Capacity
|
||||
|
||||
Renting capacity on certified nodes is charged 25% extra (x 1.25).
|
||||
|
||||
## Dedicated Nodes
|
||||
|
||||
Since April 2022, TFGrid has introduced dedicated server support. With dedicated servers, you can reserve a full server exclusively for your use. This comes with 50% discount, making it a cost-effective option.
|
||||
|
||||
Here are two examples of dedicated nodes and their prices, with maximum staking discount level (Gold => -60%) for 18 months staking:
|
||||
|
||||
- Dedicated Node 1: 192 GB memory, 24 cores, 1000 GB SSD = $75 per month
|
||||
- Dedicated Node 2: 32 GB memory, 8 cores, 1000 GB SSD = $31 per month
|
||||
|
||||
> Please check our [Cloud Pricing for utilization sheet](https://docs.google.com/spreadsheets/d/1E6MpGs15h1_flyT5AtyKp1TixH1ILuGo5tzHdmjeYdQ/edit#gid=2014089775) for more details.
|
||||
|
||||
These dedicated nodes come with a generous 5TB bandwidth usage per node per month. They are well-suited for deploying blockchain nodes or other resource-intensive workloads. Using a dedicated node requires reserving a 3node in your TFGrid admin portal. Once reserved, you have exclusive deployment rights for that node, and there are no additional costs.
|
||||
|
||||
When renting a dedicated node, you receive a 50% discount for the entire node. However, it's important to note that you will still be required to pay for the entire node, even with the discount applied. This means that while you enjoy the discount, the cost of the dedicated node is not prorated based on the resources you utilize.
|
||||
|
||||
## Staking Discount
|
||||
|
||||
| Type | Pricing Level | Nr months of TFT linked to account |
|
||||
| ---------- | ------------- | ---------------------------------- |
|
||||
| No staking | - 0% | 0 |
|
||||
| Default | - 20% | 1.5 months |
|
||||
| Bronze | - 30% | 3 months |
|
||||
| Silver | - 40% | 6 months |
|
||||
| Gold | - 60% | 18 months |
|
||||
|
||||
TFChain charges users for proof of utilization on an hourly basis. The discount applied is determined by the amount of TFT (ThreeFold Token) available in the user's TFChain account. It's important to note that the discount is calculated based on the TFT balance in the TFChain account, not on other supported blockchains like Stellar.
|
||||
|
||||
This discount mechanism operates automatically, and users don't need to take any specific actions to avail themselves of this benefit. However, it's worth mentioning that the maximum discount for network-related services is 40%.
|
||||
|
||||
### Example for 40% discount (Silver)
|
||||
|
||||
Let's break down the example for a 40% discount on Internet Capacity consumption:
|
||||
|
||||
- Suppose your consumption on the ThreeFold Grid is worth 10 TFT per hour.
|
||||
- To be eligible for a 40% discount, you need to have a minimum of 43,200 TFT in your account, calculated as 10 TFT * 24 hours * 30 days * 6 months.
|
||||
- Similarly, to be eligible for a 60% discount, you would need a minimum of 129,600 TFT in your account, calculated as 10 TFT * 24 hours * 30 days * 18 months.
|
||||
- If you have 60,000 TFT in your TFChain account, you would receive a 40% discount.
|
||||
- However, since you don't have enough tokens to qualify for the 60% discount, it won't be applicable.
|
||||
- With the 40% discount, your effective payment for the consumption would be 6 TFT per hour, as long as the amount of TFT in your account falls within the range of 43,200 to 129,600 (as calculated above).
|
||||
|
||||
Keep in mind that these calculations are based on the example provided and the specific discount levels mentioned.
|
@@ -0,0 +1,8 @@
|
||||
# Pricing
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Pricing Overview](./pricing.md)
|
||||
- [Staking Discounts](./staking_discount_levels.md)
|
||||
- [Cloud Pricing Compare](./cloud_pricing_compare.md)
|
||||
- [Grid Billing](../grid_billing/grid_billing.md)
|
@@ -0,0 +1,5 @@
|
||||
- [**Home**](@threefold_home)
|
||||
-----
|
||||
**Pricing**
|
||||
- [Cloud Pricing](@pricing)
|
||||
- [Cloud Pricing Compare](@cloud_pricing_compare)
|
@@ -0,0 +1,34 @@
|
||||
<h1>Staking Discount Levels</h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Introduction](#introduction)
|
||||
- [Table of Discounts](#table-of-discounts)
|
||||
- [Example for 40% discount](#example-for-40-discount)
|
||||
|
||||
***
|
||||
|
||||
## Introduction
|
||||
|
||||
By staking TFT on their TFChain wallet, TFGrid users can benefit to discounts up to 60%.
|
||||
|
||||
## Table of Discounts
|
||||
|
||||
| type | pricing level | nr months of TFT linked to account |
|
||||
| ---------- | ------------- | ---------------------------------- |
|
||||
| no staking | - 0% | 0 |
|
||||
| default | - 20% | 3 months |
|
||||
| bronze | - 30% | 6 months |
|
||||
| silver | - 40% | 12 months |
|
||||
| gold | - 60% | 36 months |
|
||||
|
||||
TFChain charges the user for proof_of_utilization every hour. TFChain will calculate the discount based on amount of TFT available in the account of the user on TFChain (not on Stellar or any of the other blockchains we also support). This is an automatic form of staking, the user does not have to do anything to have this benefit. For network related services its max 40% discount.
|
||||
|
||||
## Example for 40% discount
|
||||
|
||||
- I've used 10 TFT worth of Internet Capacity on tf_grid for the last hour.
|
||||
- 10TFT * 24 * 30 * 12 = I would need 86,400 TFT for one year
|
||||
- 10TFT * 24 * 30 * 36 = I would need 259,200 TFT for 3 year
|
||||
- I have 120,000 TFT in my account on TF_Chain, this means that I will get 40% discount.
|
||||
- I don't have enough tokens to get to 60% discount.
|
||||
|
@@ -0,0 +1,18 @@
|
||||
| type | pricing level | nr months of TFT linked to account |
|
||||
| ---------- | ------------- | ---------------------------------- |
|
||||
| no staking | - 0% | 0 |
|
||||
| default | - 20% | 3 months |
|
||||
| bronze | - 30% | 6 months |
|
||||
| silver | - 40% | 12 months |
|
||||
| gold | - 60% | 36 months |
|
||||
|
||||
TFChain charges the user for proof_of_utilization every hour. TFChain will calculate the discount based on amount of TFT available in the account of the user on TFChain (not on Stellar or any of the other blockchains we also support). This is an automatic form of staking, the user does not have to do anything to have this benefit. For network related services its max 40% discount.
|
||||
|
||||
### Example for 40% discount
|
||||
|
||||
- I've used 10 TFT worth of Internet Capacity on tf_grid for the last hour.
|
||||
- 10TFT * 24 * 30 * 12 = I would need 86,400 TFT for one year
|
||||
- 10TFT * 24 * 30 * 36 = I would need 259,200 TFT for 3 year
|
||||
- I have 120,000 TFT in my account on TF_Chain, this means that I will get 40% discount.
|
||||
- I don't have enough tokens to get to 60% discount.
|
||||
|
@@ -0,0 +1,89 @@
|
||||
|
||||
<h1> Resource Units </h1>
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
|
||||
- [Resource Units Overview](#resource-units-overview)
|
||||
- [Compute](#compute)
|
||||
- [Storage](#storage)
|
||||
- [Storage cost price verification Dec 2021](#storage-cost-price-verification-dec-2021)
|
||||
- [Change Log](#change-log)
|
||||
- [Remarks](#remarks)
|
||||
|
||||
***
|
||||
|
||||
## Resource Units Overview
|
||||
|
||||
The threefold Zero-OS and TFChain software translates resource units (CRU, MRU, HRU, SRU) into cloud units (CU, SU) for farming reward purposes.
|
||||
|
||||
Resource units are used to measure and convert capacity on the hardware level into cloud units: CU & SU.
|
||||
|
||||
|
||||
| Unit Type | Description | Code |
|
||||
| ------------ | ------------------------------------ | ---- |
|
||||
| Core Unit | 1 Logical Core (Hyperthreaded Core) | CRU |
|
||||
| Mem Unit | 1 GB mem | MRU |
|
||||
| HD Unit | 1 GB | HRU |
|
||||
| SSD Unit | 1 GB | SRU |
|
||||
| Network Unit | 1 GB of bandwidth transmitted in/out | NRU |
|
||||
|
||||
These are raw capacities as measured by the ThreeFold software running on Zero-OS.
|
||||
|
||||
To learn how they convert into cloudunits see [here](./resourceunits_advanced.md)
|
||||
|
||||
### Compute
|
||||
|
||||
For farming, 1 CU equals:
|
||||
|
||||
- 2 virtual CPUs with a maximum over subscription of 4 CPUs and minimum required memory of 4GB.
|
||||
- An over subscription of 4 CPUs remains still gentle as we understand many other providers use more.
|
||||
- There needs to be at least 50GB SSD per CU, if not there is penalty for nr of CU, reasoning is that otherwise people cannot deploy their VM's or Containers if there would not be minimal SSD.
|
||||
|
||||
```python
|
||||
cu = min((mru - 1) / 4, cru * 4 / 2, sru / 50)
|
||||
```
|
||||
|
||||
- 1 GB of memory is subtracted for the operating system to function.
|
||||
- please note minimal passmark per CU (with 4GB mem), needs to be 1000 passmark at farming side, this is not being checked today but might be done in future. If your chosen CPU has less than 1000 passmark per CU (of 4 GB mem), it could be your final CU's will be lower once that feature is introduced.
|
||||
|
||||
|
||||
<!-- > NOTE 17 Jan: some possible abuse has been found, we will do research how to adjust calculations to avoid this. -->
|
||||
|
||||
|
||||
### Storage
|
||||
|
||||
For farming, 1 SU equals to:
|
||||
- 1.2 TB of HD capacity (which can deliver 1 TB of net usable storage)
|
||||
- 200 GB of SSD capacity with a buffer of 20%
|
||||
|
||||
```python
|
||||
su = hru / 1200 + sru * 0.8 / 200
|
||||
```
|
||||
|
||||
#### Storage cost price verification Dec 2021
|
||||
|
||||
- price for 16 TB HDD = 300 USD
|
||||
- 16000 / 1200 = 13.3 SU
|
||||
- 1 SU costs = 300 / 13.3 = 22.5 for HDD
|
||||
- price for 2 TB SSD = 200 USD
|
||||
- 2000 * 0.8 / 200 = 8 SU
|
||||
- 1 SU costs 200 / 8 = 25 for SSD
|
||||
|
||||
|
||||
<!-- !!!include:staking_farmed_tft -->
|
||||
|
||||
## Change Log
|
||||
|
||||
- original non final specs from Summer 2021, was mentioned its not final.
|
||||
- Dec 2021 update for launch v3.x
|
||||
- there need to be at least 50 GB SSD capacity per CU
|
||||
- was in the specs of farming reward but formula above did not take it into consideration, in others nonconsistenty between specs & formula.
|
||||
- sru division to 200, was 300, to be more in line with HDD vs SSD pricing, this check needs to be done +- every 6 months, results in slightly more SU, which is good for farmers.
|
||||
- Jan 2022 update for launch v3.x
|
||||
- reverted change done in Dec, sru does not have to be deducted from cpu, results in increase of farming rewards, in other words good for farmers. Also good formula more easy.
|
||||
- Introduced warning about minimum CPU requirements in relation to passmark.
|
||||
|
||||
## Remarks
|
||||
|
||||
- There seems to be issue in simulator play.grid.tf, will check asap (17-jan)
|
||||
- We are checking all numbers & the DAO is coming life in Jan/Feb 2022, once we have the DAO every change of the specs needs to be approved by DAO voting members. For now we use the forum to notify and ask feedback and make sure farming reward goes up for the changes if possible. There ia already a minimal DAO life, the blockchain TFChain validators (L1) need to find consensus to upgrade code.
|
16
collections/manual/knowledge_base/cloud/resourceunits.md
Normal file
@@ -0,0 +1,16 @@
|
||||
## Resource Units
|
||||
|
||||
Resource units are used to measure and convert capacity on the hardware level into cloud units: CU & SU.
|
||||
|
||||
|
||||
| Unit Type | Description | Code |
|
||||
| ------------ | ------------------------------------ | ---- |
|
||||
| Core Unit | 1 Logical Core (Hyperthreaded Core) | CRU |
|
||||
| Mem Unit | 1 GB mem | MRU |
|
||||
| HD Unit | 1 GB | HRU |
|
||||
| SSD Unit | 1 GB | SRU |
|
||||
| Network Unit | 1 GB of bandwidth transmitted in/out | NRU |
|
||||
|
||||
These are raw capacities as measured by the ThreeFold software running on Zero-OS.
|
||||
|
||||
To learn how they convert into cloudunits see [here](./resourceunits_advanced.md)
|
@@ -0,0 +1,62 @@
|
||||
<h1>Resource Units Calculation</h1>
|
||||
|
||||
<h2> Table of Contents </h2>
|
||||
|
||||
- [Calculation from resource units to CU/SU for farming purposes](#calculation-from-resource-units-to-cusu-for-farming-purposes)
|
||||
- [Compute](#compute)
|
||||
- [Storage](#storage)
|
||||
- [Storage cost price verification Dec 2021](#storage-cost-price-verification-dec-2021)
|
||||
|
||||
***
|
||||
|
||||
## Calculation from resource units to CU/SU for farming purposes
|
||||
|
||||
The threefold Zero-OS and TFChain software translates resource units (CRU, MRU, HRU, SRU) into cloud units (CU, SU) for farming reward purposes.
|
||||
|
||||
## Compute
|
||||
|
||||
For farming, 1 CU equals:
|
||||
|
||||
- 2 virtual CPUs with a maximum over subscription of 4 CPUs and minimum required memory of 4GB.
|
||||
- An over subscription of 4 CPUs remains still gentle as we understand many other providers use more.
|
||||
- There needs to be at least 50GB SSD per CU, if not there is penalty for nr of CU, reasoning is that otherwise people cannot deploy their VM's or Containers if there would not be minimal SSD.
|
||||
|
||||
```python
|
||||
cu = min((mru - 1) / 4, cru * 4 / 2, sru / 50)
|
||||
```
|
||||
|
||||
- 1 GB of memory is subtracted for the operating system to function.
|
||||
- please note minimal passmark per CU (with 4GB mem), needs to be 1000 passmark at farming side, this is not being checked today but might be done in future. If your chosen CPU has less than 1000 passmark per CU (of 4 GB mem), it could be your final CU's will be lower once that feature is introduced.
|
||||
|
||||
|
||||
## Storage
|
||||
|
||||
For farming, 1 SU equals to:
|
||||
- 1.2 TB of HD capacity (which can deliver 1 TB of net usable storage)
|
||||
- 200 GB of SSD capacity with a buffer of 20%
|
||||
|
||||
```python
|
||||
su = hru / 1200 + sru * 0.8 / 200
|
||||
```
|
||||
|
||||
### Storage cost price verification Dec 2021
|
||||
|
||||
- price for 16 TB HDD = 300 USD
|
||||
- 16000 / 1200 = 13.3 SU
|
||||
- 1 SU costs = 300 / 13.3 = 22.5 for HDD
|
||||
- price for 2 TB SSD = 200 USD
|
||||
- 2000 * 0.8 / 200 = 8 SU
|
||||
- 1 SU costs 200 / 8 = 25 for SSD
|
||||
|
||||
|
||||
<!-- ## Change Log
|
||||
|
||||
- original non final specs from Summer 2021, was mentioned its not final.
|
||||
- Dec 2021 update for launch v3.x
|
||||
- there need to be at least 50 GB SSD capacity per CU
|
||||
- was in the specs of farming reward but formula above did not take it into consideration, in others nonconsistenty between specs & formula.
|
||||
- sru division to 200, was 300, to be more in line with HDD vs SSD pricing, this check needs to be done +- every 6 months, results in slightly more SU, which is good for farmers.
|
||||
- Jan 2022 update for launch v3.x
|
||||
- reverted change done in Dec, sru does not have to be deducted from cpu, results in increase of farming rewards, in other words good for farmers. Also good formula more easy.
|
||||
- Introduced warning about minimum CPU requirements in relation to passmark.
|
||||
-->
|