2006
DOI: 10.1007/11682127_22
|View full text |Cite
|
Sign up to set email alerts
|

An Energy Consumption Model for an Embedded Java Virtual Machine

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
16
0

Year Published

2007
2007
2012
2012

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 17 publications
(16 citation statements)
references
References 4 publications
0
16
0
Order By: Relevance
“…Farkas et al [3] have measured the energy consumption of the Itsy Pocket Computer and the JVM running on it. As shown in Figure 1, a JVM generally has five stages during its life cycle [12]. Farkas et al have discussed different JVMs' design trade-offs in each stage, studied their applicability to pocket computers, and measured their energy consumption.…”
Section: An Energy Consumption Framework For Distributed Java-based Smentioning
confidence: 99%
See 2 more Smart Citations
“…Farkas et al [3] have measured the energy consumption of the Itsy Pocket Computer and the JVM running on it. As shown in Figure 1, a JVM generally has five stages during its life cycle [12]. Farkas et al have discussed different JVMs' design trade-offs in each stage, studied their applicability to pocket computers, and measured their energy consumption.…”
Section: An Energy Consumption Framework For Distributed Java-based Smentioning
confidence: 99%
“…The energy consumed at the interpreter loop stage corresponds to the actual energy required to execute a Java application. The energy consumed by the other stages is constant regardless of the Java classes executed [12,13]. Lafond et al [12,13] have measured the energy consumption of each stage, and showed that the energy required for memory accesses usually accounts for 70% of the total energy consumed at all the stages.…”
Section: An Energy Consumption Framework For Distributed Java-based Smentioning
confidence: 99%
See 1 more Smart Citation
“…Energy (in µJ) is deduced from a per-bytecode energy consumption model [11], i.e., a table containing for each bytecode a corresponding energy cost (aggregating CPU instructions and memory energy costs). An array of 256 floats contains the per-bytecode energy consumption which is multiplied with the internal CPU counter array to get an estimation of the action Energy consumption.…”
Section: A Profilermentioning
confidence: 99%
“…The modifications in the VM, for adding low-level counters and implementing the energy consumption model [11], i.e., the Profiler, accounts for 2 kilobytes whereas the rest of the addition implementing the Predictor represent 14 kilobytes of Java classes.…”
Section: Memory Footprint Cost Of the Weight-watchermentioning
confidence: 99%