tfgrid/info_tfgrid
33
3
Fork 0
Code Issues Pull Requests 2 Packages Projects Releases Activity

updated pinca

Browse Source
This commit is contained in:
Mik-TF
2024-05-10 08:13:09 -04:00
parent 3aa8652dc8
commit e5d8be13b0
5 changed files with 42 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
collections/tfgrid4/boxes/cloudblock.md
View File

@@ -9,14 +9,14 @@ There are unlimited different configurations of cloudblock.
A configuration of a machine defines the cloudblock which can be made.
cloudblock can be aggregated to make a bigger cloudblock.
A cloudblock can be aggregated to make a bigger cloudblock.
The default cloudblock has
- 4GB memory
- 2 virtual cores of CPU
- minimal 50 GB of fast storage (can be more, as to be defined by provider)
- minimal availability of 1 mbit/s bandwidth at all times
- Minimal 50 GB of fast storage (can be more, as to be defined by provider)
- Minimal availability of 1 mbit/s bandwidth at all times
Terms
@@ -31,11 +31,11 @@ Terms
- 120 GB of SSD capacity
- 6.4 logical CPU core (oversubscription of 4, which means user can max use 4x CPU capacity if system allows)
- when a user choses the full machine, then he/she will have reserved all Storage Blocks capacity which means the machine is now dedicated reserved for the user, the hoster specifies the discount for this typically 50%. On a dedicated machine the user has full access to the GPU.
- min 2GB always needs to be left as buffer for memory and 10% of SSD capacity
- Min 2GB always needs to be left as buffer for memory and 10% of SSD capacity
How does it work:
- When a developer wants to deploy a virtual machine, he/she needs to define the required capacity and will be able to make a choice based on these CloudBlocks, each CloudBlock has different base specs (mem, ssd, gpu, cpu) and reputation, the developer can now make a selection of how many of these Storage Blocks need to be given to the virtual machine. This defines the monthly price which will have to be paid as well as capacity available to the VM.
- When a developer wants to deploy a virtual machine, they need to define the required capacity and will be able to make a choice based on these CloudBlocks, each CloudBlock has different base specs (mem, ssd, gpu, cpu) and reputation, the developer can now make a selection of how many of these Storage Blocks need to be given to the virtual machine. This defines the monthly price which will have to be paid as well as capacity available to the VM.
## Cloud Hour (CH)