Browser-based Edge Computing Solution for Offloading Process and Resource
Presenter: Seikown Kim
Demo from Web & Networks Interest Group
We demonstrate features of the browser-based edge computing solution, Castanets (process and resource offloading). We show renderer process offloading from one device to another for reducing both page loading time and computation time.
Transcript
The browser process runs on a low-end Smartwatch and the renderer process runs on a high-end Smartphone.
We will start with a full browsing scenario.
The HTML, JS are rendered from the Smartphone, and Smartwatch composites the result.
Clicking the links are also possible.
Again, the Smartphone renders the new page, and tiles are sent to Smartwatch for composition only.
We show the Smartphone computing JS and sending the computed result to Smartwatch.
We compare the web page loading speed.
Left is Castanets, loading browser process on TV and computes rendering on The Samsung Galaxy Android Phone.
The right is the TV itself.
Both the browser process and the renderer process are running on the same machine.
We can see that the loading speed between Castanets and the bare browser has a negligible loading time difference.
We compare the JS computation performance between Castanets and the TV browser.
JS execution for Chess is accelerated by a powerful Samsung Galaxy Android phone and took 23 seconds for the next chess move.
In the TV browser, the movement took 39.5 seconds for the next chess move.
Castanets is 40% faster.
