Commit 05b03105232f742208aa1cbe384860d685c3f18d
1 parent
f0dc0092
Broke out abstract from introduction
Showing
3 changed files
with
7 additions
and
2 deletions
include/start.tex
introduction.tex
| 1 | 1 | \section{introduction} |
| 2 | 2 | |
| 3 | +\begin{comment} | |
| 3 | 4 | Current operating systems are already proficient at managing certain system |
| 4 | 5 | resources, such as the CPU, memory, and disk. But on interactive mobile devices, |
| 5 | 6 | users care more about resources such as time, battery life, and money, that are |
| ... | ... | @@ -10,6 +11,7 @@ a metered data plan. It is the degree to which mobile devices effectively |
| 10 | 11 | manage these human-facing resources that determines a user's |
| 11 | 12 | \textit{quality of experience} (QoE), and it is QoE which should drive not just |
| 12 | 13 | policy, but decisions on mobile devices. |
| 14 | +\end{comment} | |
| 13 | 15 | |
| 14 | 16 | \begin{sloppypar} |
| 15 | 17 | While modern operating systems such as Android make decisions based on policies |
| ... | ... | @@ -37,7 +39,7 @@ frequency, such as for time-insensitive background tasks or when the performance |
| 37 | 39 | increase would not be perceivable, negative QoE may manifest itself through |
| 38 | 40 | poor battery life. |
| 39 | 41 | |
| 40 | -\newpage | |
| 42 | +%\newpage | |
| 41 | 43 | In terms of QoE, static policies can lead to resource allocation decisions that |
| 42 | 44 | are less than optimal. To remedy this, we propose designing QoE-centric |
| 43 | 45 | mobile operating systems that use QoE as input to drive resource allocation | ... | ... |