The Case for VM-Based Cloudlets in Mobile Computing
IEEE Pervasive Computing
MAUI: making smartphones last longer with code offload
Proceedings of the 8th international conference on Mobile systems, applications, and services
CODES/ISSS '10 Proceedings of the eighth IEEE/ACM/IFIP international conference on Hardware/software codesign and system synthesis
CloneCloud: elastic execution between mobile device and cloud
Proceedings of the sixth conference on Computer systems
Profiling resource usage for mobile applications: a cross-layer approach
MobiSys '11 Proceedings of the 9th international conference on Mobile systems, applications, and services
Reducing the Delay and Power Consumption of Web Browsing on Smartphones in 3G Networks
ICDCS '11 Proceedings of the 2011 31st International Conference on Distributed Computing Systems
A close examination of performance and power characteristics of 4G LTE networks
Proceedings of the 10th international conference on Mobile systems, applications, and services
Can offloading save energy for popular apps?
Proceedings of the seventh ACM international workshop on Mobility in the evolving internet architecture
Communications of the ACM
Accelerating the mobile web with selective offloading
Proceedings of the second ACM SIGCOMM workshop on Mobile cloud computing
| Hi-index | 0.00 |
In recent years, there has been growing interest in both industry and academia in augmenting mobile web browsing with support from the cloud [4, 1, 3, 16, 18]). These efforts are motivated by the goals of lowering costs of data transfer, and reducing web latencies and device energy consumption. While these efforts have adopted different approaches to cloud-based browsing, there isn't a systematic understanding of the rich design space due to the proprietary nature of many of the solutions. In this paper, we take a step towards obtaining a better understanding by evaluating an extreme point in the design space that involves cloud support for most browsing functionality including execution of JavaScript (JS), and for compaction of data (e.g., image transcoding and compression). Our study is conducted in the context of Cloud Browser (CB), a popular commercially available browser that embodies this design point. Our results indicate that CB does not provide clear benefits over Direct (a device-based browser) either in energy or download time. For e.g. while CB decreases the download time compared to Direct for 38.87% of pages, it increases it by as much as 29.8s for other pages. Similarly while CB decreases the total energy by up to 20.77J compared to Direct for 52.7% of the pages, it increases it by up to 21.31J for other pages. Interestingly, even though CB does JS execution in the cloud, it increases the CPU and network energy for close to 50% of the pages. Overall our study indicates that cloud-based browsing is not always a win, and there are important trade-offs that must be carefully considered when moving functionality to the cloud.