Migration of Web Applications with Seamless Execution

Oh, Jin-Seok; Kwon, Jin-woo; Park, Hyukwoo; Moon, Soo-Mook

doi:10.1145/2731186.2731197

Cited by 18 publications

(16 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Our offloading system is based upon previous studies [25,34] that save the execution state of a web app as the form of another web app, called the snapshot. In this section, we review how a web app works and how the snapshot is generated.…”

Section: Review Of the Web App And Snapshotmentioning

confidence: 99%

“…This article proposes a system that automatically offloads the execution of web apps without complex annotations or app instrumentation. We adopted state-of-the-art techniques used in web app migration [25,29,34], which migrates a running web app to other devices by capturing the snapshot of the web app and sending it to the destination devices. The snapshot has the form of a web app code based on HTML/CSS/JavaScript such that when executed, it automatically reconstructs the execution state (including the DOM state) and continues the app execution seamlessly from the point where it was saved.…”

Section: Introductionmentioning

confidence: 99%

“…This perfectly suits our offloading purpose, because using the snapshot, we can migrate the execution of a web app transparently to app developers. In addition, the snapshot can be captured without code instrumentation [25,34], so we can run unmodified web app codes, obviating performance degradation from running instrumented codes.…”

Section: Introductionmentioning

confidence: 99%

“…For offloading, however, the app in the client should not be terminated for continuous use of the app by the user, so we need a new architecture that can exchange the snapshot between the client and the server while the app in the client is running. Second, the previous implementation of the snapshot [25,34] takes a significant amount of time to capture and restore the web app state, so if we directly use it for offloading, the app performance will be very low or even worse than local execution (Section 4.2). In this article, we tackle those issues with a novel snapshot-based offloading system.…”

Section: Introductionmentioning

confidence: 99%

“…(1) We propose a novel approach to computation offloading in the context of web apps. We adapt and extend the snapshot, originally developed for web app migration [25,34], to transparently migrate the app execution between the client and the server when offloading computations. (2) We propose three enhancements to improve performance of the snapshot-based offloading system by reducing the overhead of capturing, restoring, and transmitting the snapshot.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Dynamic Offloading of Web Application Execution Using Snapshot

Jeong

Moon

2020

ACM Trans. Web

Self Cite

View full text Add to dashboard Cite

Mobile web platforms are facing new demands for emerging applications, such as machine learning or augmented reality, which require significant computing powers beyond that of current mobile hardware. Computation offloading can accelerate these apps by offloading the computation-intensive parts of an app from a client to a powerful server. Unfortunately, previous studies of offloading in the field of web apps have a limitation for the offloading target code or require complex user annotations, hindering the widespread use of offloading in web apps. This article proposes a novel offloading system for web apps, which can simplify the offloading process by sending and receiving the execution state of a running web app in the form of another web app called the snapshot. Since running the snapshot restores the whole app state and continues the execution from the point where it was saved, we can offload regular web app computations that affect the DOM state as well as the JavaScript state, and we do not have to pre-install the app binary at the server. Moreover, the snapshot does not require any annotations to be captured, making computation offloading more transparent to app developers. We qualitatively compared the proposed system with previous approaches in terms of programming difficulty and the scope of offloadable codes. In addition, we implemented the proposed system based on a WebKit browser and evaluated the offloading performance with five computation-intensive web apps. Our system achieved significant speedup (from 1.7 to approximately 9.0) in all of the apps, compared to local execution, which proves the feasibility of the proposed approach. CCS Concepts: • Software and its engineering → Organizing principles for web applications;

show abstract

Section: Review Of the Web App And Snapshotmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Dynamic Offloading of Web Application Execution Using Snapshot

Jeong

Moon

2020

ACM Trans. Web

Self Cite

View full text Add to dashboard Cite

show abstract

Lightweight migration for web applications with framework separation

2017

Self Cite

View full text Add to dashboard Cite

Web applications (apps) are programs created by web technologies such as HTML, CSS, and JavaScript. Web apps can be executed on any platform that supports a web browser. Such portability allows an interesting user experience called app migration, which can save an app's execution state to a file called snapshot, transmit it to another device, and continue the execution using the snapshot. However, existing approaches save all the states of the current app, regardless of its relevance to an app's state, making the snapshot size and snapshot creation time infeasibly large. For example, web apps are often programmed using web frameworks such as jQuery, which are libraries written in JavaScript to support app developments. We found that most objects created by frameworks during their initialization are not relevant to an app's state. Hence, one idea to reduce the snapshot size is not saving those framework objects in the snapshot but creating them after migration via re-initialization. Unfortunately, this is not always straightforward since the framework objects are intermingled with the app objects in the heap, possibly pointing to each other. To resolve this, we separated app objects that are attached to framework objects by monitoring app's execution and saved them to the snapshot. This paper proposes such a framework separated migration technique, with optimization to reduce the overhead, especially related to monitoring app's execution. With our approach, we could reduce the snapshot size by 89.1% on average and shorten the migration time by 47.6%, increasing the feasibility of app migration.

show abstract

ThingsMigrate: Platform‐independent migration of stateful JavaScript Internet of Things applications

et al. 2020

View full text Add to dashboard Cite

The Internet of Things (IoT) has gained wide popularity both in academic and industrial contexts. Unlike traditional embedded devices with specialized firmwares, modern IoT devices accommodate general‐purpose operating systems, allowing developers to run more sophisticated applications written in high‐level languages like JavaScript. Because IoT devices are subject to resource constraints like available battery power, we need to dynamically migrate a running process between different devices to prevent losing state. However, it is challenging to apply migration techniques using memory snapshots across the heterogeneous pool of IoT devices. We present ThingsMigrate, a middleware providing platform‐independent migration of JavaScript processes across IoT devices. Prior to execution, ThingsMigrate instruments the source code of a given program to expose its internal state. During run‐time, the transformed program produces on demand a JSON snapshot of its current state, from which new code is generated to resume execution. Thus, ThingsMigrate enables process migration entirely in the application space without any modifications to the underlying virtual machine (VM), providing VM‐independence. We present three versions of ThingsMigrate, each building on the previous to optimize for run‐time latency and memory consumption. We report on the experience of building each successive version and discuss the insights gained and the learning outcomes. We evaluated ThingsMigrate against standard benchmarks, over two IoT platforms and a cloud‐like environment. We show that it can migrate even highly CPU‐intensive applications, with average run‐time latency overhead of 33% and memory overhead of 78%. ThingsMigrate supports multiple subsequent migrations without introducing additional overhead over each subsequent migration.

show abstract

Migration of Web Applications with Seamless Execution

Cited by 18 publications

References 9 publications

Dynamic Offloading of Web Application Execution Using Snapshot

Dynamic Offloading of Web Application Execution Using Snapshot

Lightweight migration for web applications with framework separation

ThingsMigrate: Platform‐independent migration of stateful JavaScript Internet of Things applications

Contact Info

Product

Resources

About