Tactics-based remote execution for mobile computing

Rajesh Krishna Balan, Mahadev Satyanarayanan, Soyoung Park, Tadashi Okoshi

Research output: Contribution to conferencePaperpeer-review

171 Citations (Scopus)

Abstract

Remote execution can transform the puniest mobile device into a computing giant able to run resource-intensive applications such as natural language translation, speech recognition, face recognition, and augmented reality. However, easily partitioning these applications for remote execution while retaining application-specific information has proven to be a difficult challenge. In this paper, we show that automated dynamic repartitioning of mobile applications can be reconciled with the need to exploit application-specific knowledge. We show that the useful knowledge about an application relevant to remote execution can be captured in a compact declarative form called tactics. Tactics capture the full range of meaningful partitions of an application and are very small relative to code size. We present the design of a tactics-based remote execution system, Chroma, that performs comparably to a runtime system that makes perfect partitioning decisions. Furthermore, we show that Chroma can automatically use extra resources in an overprovisioned environment to improve application performance.

Original languageEnglish
Pages273-286
Number of pages14
DOIs
Publication statusPublished - 2003 May 5
Externally publishedYes
Event1st International Conference on Mobile Systems, Applications and Services, MobiSys 2003 - San Francisco, United States
Duration: 2003 May 52003 May 8

Conference

Conference1st International Conference on Mobile Systems, Applications and Services, MobiSys 2003
Country/TerritoryUnited States
CitySan Francisco
Period03/5/503/5/8

ASJC Scopus subject areas

  • Hardware and Architecture
  • Information Systems
  • Software
  • Computer Networks and Communications

Fingerprint

Dive into the research topics of 'Tactics-based remote execution for mobile computing'. Together they form a unique fingerprint.

Cite this