Report on the third workshop on hot topics in software upgrades (HotSWUp'11)

Hayden, Christopher M.; Neamtiu, Iulian

doi:10.1145/2146382.2146399

Cited by 1 publication

(1 citation statement)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The update process should not lose or corrupt the application execution. Such a corruption occurs when the update alters local variables or control-flow of a method in any execution stack [HN12]. In our example, if the render thread enters the Vector3D»length method and the update is applied before the Vector3D»squareSum method is called, continuing the execution of the length method will fail as the Vector3D » squareSum method does not exist anymore.…”

Section: Change Challenges Illustratedmentioning

confidence: 99%

Dynamic Software Update from Development to Production.

Tesone¹,

Polito²,

Bouraqadi³

et al. 2018

JOT

View full text Add to dashboard Cite

Dynamic Software Update (DSU) solutions update applications while they are executing. These solutions are typically used in production to minimize application downtime, or in integrated development environments to provide live programming support. Each of these scenarios presents different challenges, forcing existing solutions to be designed with only one of these use cases in mind. For example, DSUs for live programming typically do not implement safe point detection or instance migration, while production DSUs require manual generation of patches and lack IDE integration. Also, these solutions have limited ability to update themselves or the language core libraries, and some of them present execution penalties outside the update window. We propose a DSU (gDSU) that works for both live programming and production environments. Our solution implements safe update point detection using call stack manipulation and a reusable instance migration mechanism to minimize manual intervention in patch generation. Moreover, it also offers updates of core language libraries and the update mechanism itself. This is achieved by the incremental copy of the modified objects and an atomic commit operation. We show that our solution does not affect the global performance of the application and it presents only a run-time penalty during the update window. Our solution is able to apply an update impacting 100,000 instances in 1 second. In this 1 second, only during 250 milliseconds the application is not responsive. The rest of the time the application runs normally while gDSU is looking for the safe update point. The update only requires to copy the elements that are modified.

show abstract

Section: Change Challenges Illustratedmentioning

confidence: 99%