## 3 Results Analysis
### Experimental Results for Sleep Measurements
#### 3.2.4 Summary of Sleep Functions Experiment Results  
The results presented above are collected in Table 2. It consists of the main statistical parameters of experiment datasets: median, MAD, minimum and maximum values. Statistical parameters are provided for the different conditions of the experiments: investigated function (_HPTSleep_ or _uSleep()_, platform or experimental environment (Host OS, QEMU, ESXi, Xen, and Vbox) and the load type under which the experiment was performed (idle System, CPU-bound, and IO/network-bound). \begin{table}
\begin{tabular}{l l l r r r r} \hline \hline
**Function** & **Platform** & **Load** & **MAD, ns** & **Max, ns** & **Median, ns** & **Min, ns** \\ \hline HPTSleep & ESXi & CPU-bound & 18.6 & 287,997,000.0 & 113.9 & 66.6 \\ HPTSleep & ESXi & IO/network-bound & 14.3 & 2,024,870.0 & 116.7 & 65.2 \\ HPTSleep & ESXi & Idle System & 6.4 & 432,825.0 & 95.2 & 65.2 \\ HPTSleep & Host OS & CPU-bound & 3.6 & 196,002,000.0 & 102.4 & 82.3 \\ HPTSleep & Host OS & IO/network-bound & 2.9 & 407,121.0 & 94.9 & 79.1 \\ HPTSleep & Host OS & Idle System & 0.7 & 402,269.0 & 82.0 & 72.0 \\ HPTSleep & QEMU & CPU-bound & 2.9 & 208,008,000.0 & 136.8 & 96.7 \\ HPTSleep & QEMU & IO/network-bound & 0.7 & 4,351,030.0 & 117.8 & 74.8 \\ HPTSleep & QEMU & Idle System & 1.4 & 1,187,960.0 & 116.4 & 74.8 \\ HPTSleep & VBox & CPU-bound & 76.1 & 596,501,000.0 & 5183.1 & 2161.1 \\ HPTSleep & VBox & IO/network-bound & 125.0 & 12,048,600.0 & 5087.4 & 2134.6 \\ HPTSleep & VBox & Idle System & 121.1 & 4,697,970.0 & 5117.3 & 2142.5 \\ HPTSleep & Xen & CPU-bound & 2.9 & 355,964,000.0 & 94.5 & 58.7 \\ HPTSleep & Xen & IO/network-bound & 3.6 & 9,644,930.0 & 127.5 & 87.4 \\ HPTSleep & Xen & Idle System & 4.3 & 573,593.0 & 94.5 & 67.3 \\ uSleep & ESXi & CPU-bound & 294.3 & 196,105,000.0 & 56,044.5 & 4883.0 \\ uSleep & ESXi & IO/network-bound & 1123.6 & 12,689,600.0 & 62,199.1 & 6365.4 \\ uSleep & ESXi & Idle System & 851.4 & 1,272,060.0 & 63,085.2 & 4300.1 \\ uSleep & Host OS & CPU-bound & 55.2 & 69,705,100.0 & 54,674.9 & 5918.4 \\ uSleep & Host OS & IO/network-bound & 792.7 & 4,971,040.0 & 57,756.1 & 5478.3 \\ uSleep & Host OS & Idle System & 680.0 & 689,113.0 & 61,996.3 & 6848.2 \\ uSleep & QEMU & CPU-bound & 290.0 & 693,720,000.0 & 63,264.2 & 7132.5 \\ uSleep & QEMU & IO/network-bound & 3738.6 & 11,674,900.0 & 74,540.7 & 7807.0 \\ uSleep & QEMU & Idle System & 1820.0 & 4,150,180.0 & 97,351.3 & 8167.9 \\ uSleep & VBox & CPU-bound & 3,611,915.2 & 539,619,000.0 & 7,601,230.0 & 15913.7 \\ uSleep & VBox & IO/network-bound & 16,410.0 & 11,469,400.0 & 131,192.0 & 29,421.1 \\ uSleep & VBox & Idle System & 16,395.5 & 8,670,880.0 & 131,252.0 & 29,471.2 \\ uSleep & Xen & CPU-bound & 229.8 & 141,160,000.0 & 98,544.0 & 10,624.7 \\ uSleep & Xen & IO/network-bound & 935.0 & 3,924,120.0 & 107,852.0 & 23,060.8 \\ uSleep & Xen & Idle System & 260.0 & 2,176,090.0 & 109,411.0 & 24,399.8 \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Results for all experiments with sleep functions. Figure 15: CCDF representation of measurements of miss time for the IO/network testbed. Further, similar to the time acquisition function overhead, ANOVA on ranks analysis was performed to determine which factors affect significantly the same parameters of sleep miss values. Function, load and platform columns of the table are considered as the different factors. Kruskal-Wallis analysis on ranks and post hoc tests using [PERSON]'s test of timer cost datasets were also used. Kruskal-Wallis rank analysis of medians, MADs, minimum and maximum variables show that type of the sleep function is a significant factor for all virtualization types. As in the case of time acquisition experiments discussion, virtualization is a significant factor only on the Virtual Box as a virtualization platform. The load type only significantly affects the max values. Interaction between factors function and platform significantly affects the median, MAD and min values, but not the max. Interaction between factors platform and load only affects max values.