this is for holding javascript data
Henri van den Bulk edited subsection_Resource_Locality_Devices_that__.tex
almost 9 years ago
Commit id: 8f7fa1171d0b814a334b2b838beeccf006b9411b
deletions | additions
diff --git a/subsection_Resource_Locality_Devices_that__.tex b/subsection_Resource_Locality_Devices_that__.tex
index 6225b36..2ec71ea 100644
--- a/subsection_Resource_Locality_Devices_that__.tex
+++ b/subsection_Resource_Locality_Devices_that__.tex
...
The cost of handing of the task is based on a couple of factors. One, the network latency which is a combination of the distance to the resource and the bandwidth of the connections between the two endpoints. Second, the bandwidth of the computing resources and the time it takes those resources to compute.
For obvious reasons if we can reduce the distance between the device and the compute resources we will reduce latency. This attribution of latency can be modeled as
a weight $ \{ \alpha \} $. The network controller will need to find the closest resource that's not loaded, i.e. that has compute
capacity availability. This concept we'll refer to the resource locality.