edits
parent
3cb139d3dd
commit
233280cbee
|
@ -59,9 +59,6 @@ We further conduct several experiments to confirm our observations from \Cref{se
|
|||
(iii) the adaptive app pattern is not unique to facebook,
|
||||
(iv) apps spend significant time below $\fenergy$.
|
||||
|
||||
\todo{FIXME}
|
||||
\fixme{Change clustergraph labels: Kiss 70 => Kiss}
|
||||
|
||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||
\paragraph{Evaluation platform}
|
||||
|
||||
|
|
|
@ -21,8 +21,6 @@ Launch screen on; idle & 130 \\
|
|||
\label{fig:item_energy_cost}
|
||||
\end{figure}
|
||||
|
||||
\todo{FIXME}
|
||||
|
||||
CPUs consume considerable energy on mobile phones.
|
||||
As Table \ref{fig:item_energy_cost} shows, a single (big) CPU core on a Pixel 2, running at full speed with the screen off, consumes almost three times the energy of the display, and a second core running at full speed almost doubles that.
|
||||
On typical mobile phones, these high costs are mitigated by running the CPU at a slower speed (frequency) to save energy.
|
||||
|
|
Loading…
Reference in New Issue