A methodology for evaluating JavaScript execution behavior in interactive web applications

Abstract

JavaScript has gone from being a mechanism for providing dynamic web pages to an important component of many web applications. Currently one of the most popular type of web applications is so-called social networks, e.g., Facebook, Twitter, and MySpace. However, the workload and execution behavior of JavaScript in this context have not been fully explored or understood.In this paper we present a methodology for characterizing the JavaScript execution behavior in interactive web applications using deterministic execution of use cases. Then, we apply this methodology to evaluate a set of social network applications and compare their behavior to a set of established JavaScript benchmarks. Our results confirm previous studies that the execution behavior of social networks differ from established benchmarks. In addition, we identify one novel difference not published before, i.e., the use of anonymous functions in web applications.978-1-4577-0476-5/11/$26.00

Heuristics for Thread-Level Speculation in Web Applications

“…To validate the correctness of our TLS implementation we have compared the committed bytecode instructions, the return values, and all written data values in our TLS implementation with the sequential execution trace. The full methodology is described in [8].…”

“…[8], [9], [10]. One of the consequences is that JIT often increases the execution times in web applications, while TLS decreases the execution times [8], [7].…”

“…[8], [9], [10]. One of the consequences is that JIT often increases the execution times in web applications, while TLS decreases the execution times [8], [7]. A study by Fortuna et al [11] shows potential JavaScript speedups of up to 45 times with parallelism in web applications.…”

“…They found that they were able to make execution 2.8 times faster for well known JavaScript benchmarks. Unfortunately, large loop structures are rare in real web applications [8].…”

Practice and Evaluation of Pagelet-Based Client-Side Rendering Mechanism

“…We need to keep track of what elements are being loaded on each webpage. Client side uses JavaScript libraries that often contain massive amounts of functions, inside which only a handful of those functions are used actually in total execution time [35]. Therefore, in order to speed up presenting webpage, we remove any render-blocking JavaScript or CSS that is not being used on the webpage by using PageSpeed Insights [43].…”