this is for holding javascript data
Henri van den Bulk edited subsection_Resource_Locality_Devices_that__.tex
almost 9 years ago
Commit id: c204fd8bd0025d3345df05a7bc134ed0a6d506d5
deletions | additions
diff --git a/subsection_Resource_Locality_Devices_that__.tex b/subsection_Resource_Locality_Devices_that__.tex
index 8842c85..29bea47 100644
--- a/subsection_Resource_Locality_Devices_that__.tex
+++ b/subsection_Resource_Locality_Devices_that__.tex
...
\subsection{Resource Locality}
Devices that are seeking to leverage cloud based computing for offloading computing needs need to be in close proximity to the computing resources. By having the computing resources close it will allow the trade off between compute power and network latency be more economical.
The notion of resource locality is important when resources that are needed are distributed. For example in OpenPipes, which is a platform to allow hardware be distributed across physical resources, only connected via an SDN solution.
If a device needs to perform a computational task that it has limited resources for or does not have that capability, e.g. matrix multiplication, it will need to make a trade off what's the cost of performing the computation on the device or cost of sending off the computation.