Commit 0818c6e0782176feb8767bf513013db525963503
1 parent
f092c4d9
spelling corrections
Showing
3 changed files
with
11 additions
and
11 deletions
abstract.tex
| ... | ... | @@ -7,7 +7,7 @@ mobile devices. What is urgently needed is a way to put energy consumption in |
| 7 | 7 | context by measuring the value delivered by mobile apps. An accurate value |
| 8 | 8 | measure would enable cross-app comparison, app improvement, energy virus |
| 9 | 9 | detection, and effective runtime energy allocation and prioritization. Given |
| 10 | -that gains in modeling will be lost without a measure of value, we believe | |
| 10 | +that gains in modelling will be lost without a measure of value, we believe | |
| 11 | 11 | that this is the most important open problem in energy management. Our paper |
| 12 | 12 | motivates the problem, describes requirements for a candidate value measure, |
| 13 | 13 | discusses possible inputs to such a metric, and presents result from a | ... | ... |
results.tex
| ... | ... | @@ -6,7 +6,7 @@ large dataset of energy consumption measurements collected by an IRB-approved |
| 6 | 6 | experiment run on the \PhoneLab{} testbed. \PhoneLab{} is a public smartphone |
| 7 | 7 | platform testbed located at the University at |
| 8 | 8 | Buffalo~\cite{phonelab-sensemine13}. 220~students, faculty, and staff carry |
| 9 | -instrumented Android Nexus~5 smartphones and receiv subsidized service in | |
| 9 | +instrumented Android Nexus~5 smartphones and receive subsidized service in | |
| 10 | 10 | return for willingness to participate in experiments. \PhoneLab{} provides |
| 11 | 11 | access to a representative group of participants balanced between genders and |
| 12 | 12 | across a wide variety of age brackets, making our results more |
| ... | ... | @@ -85,7 +85,7 @@ looked better when their foreground usage was considered. |
| 85 | 85 | Finally, we the data we collected by instrumenting the |
| 86 | 86 | \texttt{SurfaceFlinger} and \texttt{AudioFlinger} components to compute a |
| 87 | 87 | simple measure of content delivery. We measure the audio and video frame |
| 88 | -rates and combine them into a single measure by using bitrates corresponding | |
| 88 | +rates and combine them into a single measure by using bit-rates corresponding | |
| 89 | 89 | to a 30~fps YouTube-encoded video and 128~kbps two-channel audio, with the |
| 90 | 90 | weights representing the fact that a single frame of video contains much more |
| 91 | 91 | content than a single sample of audio. We use this combined metric as the | ... | ... |
usage.tex
| ... | ... | @@ -36,12 +36,12 @@ respectively: |
| 36 | 36 | % |
| 37 | 37 | \begin{enumerate} |
| 38 | 38 | |
| 39 | -\item An adversary will require you to remove some number of apps from your | |
| 39 | +\item An advisory will require you to remove some number of apps from your | |
| 40 | 40 | smartphone. Order the apps you are currently using from least important to |
| 41 | 41 | most important. The N least important apps will be removed. |
| 42 | 42 | |
| 43 | 43 | \item Your smartphone will require you to create an energy budget for the |
| 44 | -apps you use. During any discharging cycle, once an app runs out of energy | |
| 44 | +apps you use. During any discharging cycle, once an app runs out of energy quota | |
| 45 | 45 | you will not be able to use it until you plug in your smartphone. Allocate |
| 46 | 46 | battery percentages to each app you use. |
| 47 | 47 | |
| ... | ... | @@ -54,7 +54,7 @@ the second experiment to make it more similar to the first, the adversary |
| 54 | 54 | could remove the apps consuming the least energy up to a given target. |
| 55 | 55 | |
| 56 | 56 | For our value measure we are hopeful that users will prove capable of |
| 57 | -assiging cardinal utilities to apps---as in the second experiment---since | |
| 57 | +assigning cardinal utilities to apps---as in the second experiment---since | |
| 58 | 58 | this matches most directly with our proposed value measure and could provide |
| 59 | 59 | ground truth for a value measure computed automatically. The second |
| 60 | 60 | experiment also engages users directly in the task of allocating energy, |
| ... | ... | @@ -85,10 +85,10 @@ The most powerful use of a value measure would be to compare apps by |
| 85 | 85 | comparing their energy efficiency, therefore overcoming the most critical |
| 86 | 86 | flaw in current attempts to compare or categorize apps by their energy |
| 87 | 87 | consumption alone~\cite{carat-sensys13}. Consider attempting to compare a |
| 88 | -chat client and videoconferencing app by only measuring their energy | |
| 88 | +chat client and video-conferencing app by only measuring their energy | |
| 89 | 89 | consumption. Unless it is terribly written, the chat client will consume less |
| 90 | 90 | energy. But this does not mean that it is efficient, or that the |
| 91 | -videconferencing app is not. Ultimately, all the energy consumption | |
| 91 | +video-conferencing app is not. Ultimately, all the energy consumption | |
| 92 | 92 | comparison truly reveals is that the two apps do different things---which we |
| 93 | 93 | knew. |
| 94 | 94 | |
| ... | ... | @@ -104,7 +104,7 @@ By computing value and, thus, energy efficiency, we can overcome these |
| 104 | 104 | weaknesses. A value measure should allow us to compare the efficiency of two |
| 105 | 105 | apps in different categories based on how efficiently they use energy to |
| 106 | 106 | deliver user value, making it possible to compare games to email clients to |
| 107 | -video players. Comparisons within the same app category shoud allow users to | |
| 107 | +video players. Comparisons within the same app category should allow users to | |
| 108 | 108 | select the most efficient email client or web browser. Aggregating results |
| 109 | 109 | over all users, differences in app energy efficiency should reflect how well |
| 110 | 110 | the app is written and how well it predicts and adapts to users, not just |
| ... | ... | @@ -132,7 +132,7 @@ defer work on everything else. |
| 132 | 132 | A measure of app value makes it possible to produce a rigorous definition of |
| 133 | 133 | the term \textit{energy virus}: an app that produces little to no value per |
| 134 | 134 | joule. The choice of threshold will require some study, as it is unlikely |
| 135 | -impossible to produce a single efficiency cutoff that cleanly separates | |
| 135 | +impossible to produce a single efficiency cut-off that cleanly separates | |
| 136 | 136 | malicious apps from ones that are merely poorly-written. Note also that this |
| 137 | 137 | definition of energy virus can be made on a per-user basis. This is important |
| 138 | 138 | since a non-malicious but poorly-written app that continues to consume energy |
| ... | ... | @@ -154,7 +154,7 @@ However, all of these previous efforts have ignored the critical question of |
| 154 | 154 | mechanisms are, systems that rely on rates will fail if they provide the same |
| 155 | 155 | rate to Skype and Snapchat, or to a very efficient app and an energy virus. |
| 156 | 156 | |
| 157 | -A measure of value can be used alone or in conjuction with energy consumption | |
| 157 | +A measure of value can be used alone or in conjunction with energy consumption | |
| 158 | 158 | to help prioritize limited energy resources. The simplest approach is to |
| 159 | 159 | attempt to enforce an energy allocation based on the relative value assigned |
| 160 | 160 | to each app. To encourage apps to be more energy efficient, it may also be | ... | ... |