Proceedings of the 14th International Conference on Compilers, Architectures and Synthesis for Embedded Systems 2011
DOI: 10.1145/2038698.2038703
|View full text |Cite
|
Sign up to set email alerts
|

Selective just-in-time compilation for client-side mobile javascript engine

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2012
2012
2016
2016

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 10 publications
(4 citation statements)
references
References 7 publications
0
4
0
Order By: Relevance
“…However, we assume no knowledge about the underlying JIT compilation mechanism -instead, we expect to draw all necessary conclusions from our collected data. On the other hand, there are several other studies that focus on tuning the underlying JavaScript JIT compilation mechanism to improve performance [12,21,22,23,24] or on selecting the best JavaScript framework to program with [17]. For instance, Lee and Moon [22] study, for mobile web browsers, how the JIT engine can be turned on or off in order to avoid waiting for the compilation of a code that may be not frequently executed enough to pay off the compilation time.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…However, we assume no knowledge about the underlying JIT compilation mechanism -instead, we expect to draw all necessary conclusions from our collected data. On the other hand, there are several other studies that focus on tuning the underlying JavaScript JIT compilation mechanism to improve performance [12,21,22,23,24] or on selecting the best JavaScript framework to program with [17]. For instance, Lee and Moon [22] study, for mobile web browsers, how the JIT engine can be turned on or off in order to avoid waiting for the compilation of a code that may be not frequently executed enough to pay off the compilation time.…”
Section: Related Workmentioning
confidence: 99%
“…On the other hand, there are several other studies that focus on tuning the underlying JavaScript JIT compilation mechanism to improve performance [12,21,22,23,24] or on selecting the best JavaScript framework to program with [17]. For instance, Lee and Moon [22] study, for mobile web browsers, how the JIT engine can be turned on or off in order to avoid waiting for the compilation of a code that may be not frequently executed enough to pay off the compilation time. Furthermore, mobile web browsers are such an important cellphone use case that they deserve a specific study on how to render pages with the minimum use of battery: Zhu and Vijay [31] analyze how to leverage heterogeneous multiprocessor systems to render mobile web pages fast enough to the user while maximizing power efficiency.…”
Section: Related Workmentioning
confidence: 99%
“…In the multi-core environment, they improved performance by 6 % on average and up to 34 % over the conventional trace-based JIT. These history-based approaches, however, may not be applicable to the real world [23]. Along with JIT compilation, many others have proposed JavaScript acceleration by dynamic parallelization.…”
Section: Javascript Accelerationmentioning
confidence: 99%
“…The work by Lee et al [23] provides good insight regarding whether JavaScript engines should put so much effort into compiling all the script to avoid interpretation. Benchmark software exhibit many opportunities for hot traces to be compiled into extremely efficient native code but real web pages' JavaScript code does not necessarily contain so many instructions being called again and again.…”
Section: Combined Jit Frameworkmentioning
confidence: 99%