2009
DOI: 10.1007/978-3-642-01802-2_28
|View full text |Cite
|
Sign up to set email alerts
|

Developing and Benchmarking Native Linux Applications on Android

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

2
15
0

Year Published

2012
2012
2018
2018

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 29 publications
(17 citation statements)
references
References 5 publications
2
15
0
Order By: Relevance
“…In particular, Android applications are known to suffer from several limitations that negatively affect their performance in time critical scenarios. This is partly due to the overhead introduced by the DVM, as confirmed by recent experimental studies and also by our performance results [14,15]. Benchmarking results [15] indicate that native C Android applications can be up to 30 times as fast as an identical algorithm running in the DVM.…”
Section: Related Worksupporting
confidence: 88%
See 1 more Smart Citation
“…In particular, Android applications are known to suffer from several limitations that negatively affect their performance in time critical scenarios. This is partly due to the overhead introduced by the DVM, as confirmed by recent experimental studies and also by our performance results [14,15]. Benchmarking results [15] indicate that native C Android applications can be up to 30 times as fast as an identical algorithm running in the DVM.…”
Section: Related Worksupporting
confidence: 88%
“…This is partly due to the overhead introduced by the DVM, as confirmed by recent experimental studies and also by our performance results [14,15]. Benchmarking results [15] indicate that native C Android applications can be up to 30 times as fast as an identical algorithm running in the DVM. Although this issue is partly addressed by the introduction of the Dalvik Just In Time (JIT) compiler (from Android version 2.2 on), other performance pitfalls are introduced by the Dalvik memory management mechanisms.…”
Section: Related Worksupporting
confidence: 88%
“…[18][19][20][21][22] We extracted from that material all publicly available codes that fit the categories of the proposed class library. In many cases, the original code was available only in Java or only in C/C++.…”
Section: Library Of Code Snippets For the Generation Of Synthetic Promentioning
confidence: 99%
“…When the test operation is completed, the metrics are collected and stored (lines [17][18][19][20][21][22][23][24][25][26][27].…”
Section: Figurementioning
confidence: 99%
“…We use java native interface (JNI), an efficient approach to call C program from Java program on Android [11], for profiling points to call the time profiling component. The time profiling component is implemented as JNI native library which will be loaded when the application starts to execute.…”
Section: Time Profiling Componentsmentioning
confidence: 99%