1 / 19

ThinkAir : Dynamic Resource Allocation and Parallel Execution in Cloud for Mobile Code Offloading

ThinkAir : Dynamic Resource Allocation and Parallel Execution in Cloud for Mobile Code Offloading. Sokol Kosta , Pan Hui Deutsche Telekom Labs, Berlin, Germany Andrius Aucinas , Richard Mortier University of Cambridge, Cambridge, UK Xinwen Zhang

vadin
Download Presentation

ThinkAir : Dynamic Resource Allocation and Parallel Execution in Cloud for Mobile Code Offloading

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ThinkAir: Dynamic Resource Allocation and Parallel Execution in Cloud for Mobile Code Offloading SokolKosta, Pan Hui Deutsche Telekom Labs, Berlin, Germany AndriusAucinas, Richard Mortier University of Cambridge, Cambridge, UK Xinwen Zhang Huawei Research Center, Santa Clara, CA, USA IEEE INFOCOM 2012

  2. Prominent Related Works • MAUI(2010) • Provides method level code offloading based on .NET framework. • Does not address the scaling of execution in cloud. • CloneCloud(2011) • Provides offline static analysis of different running condition of the process binary, and build a database of pre-computed partitions. • Limited input/environment conditions, and needs to be bootstrapped for every new apps.

  3. ThinkAir • A framework that exploits the concept of smart phone virtualization in the cloud, and provides method-level computation offloading. • Parallelizing method execution using multiple VM images. • On-demand resource allocation. • Online method-level offloading.

  4. Design Goals • Dynamic adaptation to changing environment. • Ease of use for developers. • Performance improvement through cloud computing. • Dynamic scaling of computation power.

  5. Overview • Annotate methods with @Remote.

  6. Execution Controller • Make offloading decisions. • Four policies: • Execution time • Energy • Execution time andenergy • Execution time, energy, and cost.

  7. Client Handler • Code execution • Manage connection. • Execute code. • Return results. • VM management • Add VM with more computing power or resources. • Distributes task among VMs, and collects results.

  8. Cloud Infrastructure • OS: customized version of Android x86. • 6 types of VM. • VM Resume latency: • Paused: 300ms • Up to 7s if too many VMs are resumed simultaneously. • Powered-off: 32s

  9. Profilers • Hardware profiler • CPU, Screen, WiFi, 3G • Software profiler • Use Android Debug API to record information. • Network profiler

  10. Energy Estimation Model • Modify the original PowerTutor model. • PowerTutor[1] model • CPU, LCD screen, GPS, WiFi, 3G, and audio interface. • HTC Dream phone. [1] Accurate online power estimation and automatic battery behavior based power model generation for smartphones, CODES/ISSS ’10

  11. Experiment Setup • BIV(boundary input value) • The minimum value of the input parameter for which offloading would give a benefit. • Offloading policy: execution time. • Different Scenarios: • Phone • WiFi-Local (RTT 5ms) • router attached to cloud server. • WiFi-Internet (RTT 50ms) • 3G (RTT 100ms)

  12. Micro-Benchmark[2] Results • Network latency clearly affects the BIV. [2] http://kano.net/javabench/

  13. N-Queen Results • BIV = 5

  14. N-Queen Results(Cont.) • N=8 • Different CPU energy consumed • Due to bandwidth and latency of the links, and subsequently affected the time spent waiting for results and in transmission.

  15. Face Detection Results • Counts the number of faces in a picture. • Photos are loaded in both device and cloud.

  16. Face Detection Results(Cont.) • 100 pictures

  17. Virus Scanning Results • Total size of files: 10MB • Number of files: ~3,500 • CPU energy consumption is lower when offloading using 3G.

  18. Parallelization with Multiple VM Clones • Workloads are evenly distributed among VMs. • Clones are resumed from pause state.

  19. Conclusion • ThinkAir is a framework for offloading mobile computation to the cloud, with the ability of on-demand VM resource scaling. • The authors will continue to work on improving programmer support for parallelizable applications, since they think ita key direction to use the capabilities of distributed computing of the cloud.

More Related