s
This commit is contained in:
@@ -8,6 +8,6 @@ Cloud units are the basis for buying & selling capacity on the ThreeFold Grid (f
|
||||
|
||||
|
||||
References:
|
||||
- Cloud units the the building blocks for any Cloud / IT workload. See definition [here](https://library.threefold.me/info/threefold#/tfgrid/farming/threefold__resource_units_calc_cloudunits)
|
||||
- Cloud units the the building slice for any Cloud / IT workload. See definition [here](https://library.threefold.me/info/threefold#/tfgrid/farming/threefold__resource_units_calc_cloudunits)
|
||||
- Cloud units are also used to determine commercial pricing for utilisation. See definition [here](https://library.threefold.me/info/threefold#/cloud/threefold__pricing?id=discount-levels)
|
||||
- Low level primitive [cloud functions](https://library.threefold.me/info/threefold/#/technology/threefold__tfgrid_primitives)
|
||||
@@ -31,7 +31,7 @@ Context switches are essential for multitasking, but they come with overhead tha
|
||||
|
||||
3. **Resource Contentions**: Context switches can exacerbate resource contention issues, especially in systems with limited CPU cores. If multiple processes are frequently contending for CPU time, the overhead of context switches can further delay process execution.
|
||||
|
||||
4. **Fragmentation**: Frequent context switches can lead to memory fragmentation, as processes are loaded and unloaded into memory. This fragmentation can degrade system performance over time, as it becomes more challenging to find contiguous blocks of memory for new processes.
|
||||
4. **Fragmentation**: Frequent context switches can lead to memory fragmentation, as processes are loaded and unloaded into memory. This fragmentation can degrade system performance over time, as it becomes more challenging to find contiguous slice of memory for new processes.
|
||||
|
||||
While context switches are necessary for multitasking, excessive context switching can indeed lead to a significant loss of execution power by introducing overhead and resource contention in the system.
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ Imagine a storage system with the following benefits
|
||||
|
||||
Our storage architecture follows the true peer-to-peer design of the TF grid. Any participating node only stores small incomplete parts of objects (files, photos, movies, databases...) by offering a slice of the present (local) storage devices. Managing the storage and retrieval of all of these distributed fragments is done by a software that creates development or end-user interfaces for this storage algorithm. We call this '**dispersed storage**'.
|
||||
|
||||
Peer-to-peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. Also, you might want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
|
||||
Peer-to-peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. Also, you might want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture and could be built by using the same building slice produced by farmers and consumed by developers or end-users.
|
||||
|
||||
|
||||
!!!include:qsss_toc
|
||||
|
||||
@@ -24,7 +24,7 @@ The cloud user can mix and match storage technologies as are required for their
|
||||
|
||||
## Peer2Peer Advantages
|
||||
|
||||
Peer2peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. You might also want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture, and could be built by using the same building blocks produced by farmers and consumed by developers or end-users.
|
||||
Peer2peer provides the unique proposition of selecting storage providers that match your application and service of business criteria. For example, you might be looking to store data for your application in a certain geographic area (for governance and compliance) reasons. You might also want to use different "storage policies" for different types of data. Examples are live versus archived data. All of these uses cases are possible with this storage architecture, and could be built by using the same building slice produced by farmers and consumed by developers or end-users.
|
||||
|
||||
> There is 100% control over where the data is positioned and the security is incredible.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user