diff options
| author | ORGERIE Anne-Cecile <anne-cecile.orgerie@inria.fr> | 2019-07-19 12:19:55 +0200 |
|---|---|---|
| committer | ORGERIE Anne-Cecile <anne-cecile.orgerie@inria.fr> | 2019-07-19 12:19:55 +0200 |
| commit | f00c6bdae328699caf101255ac435adc4e17eade (patch) | |
| tree | e465523fa49c432b4ebfb541e3d5c3f603c70ccc /2019-ICA3PP.org | |
| parent | b2adf2caf0697a613d63903b3dccbed65902ce70 (diff) | |
conclusion
Diffstat (limited to '2019-ICA3PP.org')
| -rw-r--r-- | 2019-ICA3PP.org | 94 |
1 files changed, 62 insertions, 32 deletions
diff --git a/2019-ICA3PP.org b/2019-ICA3PP.org index 85b5829..bfb9b95 100644 --- a/2019-ICA3PP.org +++ b/2019-ICA3PP.org @@ -315,7 +315,7 @@ and transmission technologies. randomly in a rectangle of $400m^2$ around the AP which corresponds to a typical use case for a home environment. All the cell nodes employ the default WIFI energy model provided by ns3. The different - energy values used by the energy model are provided on Table \ref{tab:wifi-energy}. These parameters + energy values used by the energy model are provided in Table 1. These parameters were extracted from previous work\cite{halperin_demystifying_nodate,li_end--end_2018} On IEEE 802.11n. Besides, we suppose that the energy source of each nodes is not limited during the experiments. Thus each node @@ -366,7 +366,7 @@ and transmission technologies. model for the dynamic energy consumption \cite{sivaraman_profiling_2011,Serrano2015}, and it includes also a static energy consumption. The different values used to instantiate the ECOFEN energy model for the - network part are shown in Table \ref{tab:net-energy} and come from previous work + network part are shown in left part of Table 1 and come from previous work \cite{cornea_studying_2014-1}. ** Cloud Part @@ -460,8 +460,8 @@ In our case with small and sporadic network traffic, these results show that wit #+BEGIN_EXPORT latex \begin{figure} \centering - \includegraphics[width=0.6\linewidth]{./plots/numberSensors-WIFINET.png} - \caption{Analysis of the variation of the number of sensors on the IoT/Network part energy consumption.} + \includegraphics[width=0.5\linewidth]{./plots/numberSensors-WIFINET.png} + \caption{Analysis of the variation of the number of sensors on the IoT/Network part energy consumption for a transmission interval of 10s.} \label{fig:sensorsNumber} \end{figure} #+END_EXPORT @@ -476,6 +476,16 @@ In our case with small and sporadic network traffic, these results show that wit the PUE to include the external energy costs like server cooling and data center facilities \cite{Ehsan}. + #+BEGIN_EXPORT latex + \begin{figure} + \centering + \includegraphics[width=0.8\linewidth]{./plots/vmSize-cloud.png} + \caption{Server power consumption multiplied by the PUE (= 1.2) using 20 sensors sending data every 10s for various VM memory sizes} + \label{fig:vmSize} + \end{figure} + #+END_EXPORT + + Firstly, we analyze the impact of the VM allocated memory on the server energy consumption. Figure \ref{fig:vmSize} depicts the server energy consumption according to the VM allocated memory for 20 sensors sending data every 10s. Note that @@ -488,15 +498,6 @@ In our case with small and sporadic network traffic, these results show that wit heavy memory accesses and processing time. Thus, remaining experiments are based on VM with 1024MB of allocated memory. - #+BEGIN_EXPORT latex - \begin{figure} - \centering - \includegraphics[width=0.8\linewidth]{./plots/vmSize-cloud.png} - \caption{Server power consumption multiplied by the PUE (= 1.2) using 20 sensors sending data every 10s for various VM memory sizes} - \label{fig:vmSize} - \end{figure} - #+END_EXPORT - Next, we study the effects of increasing the number of sensors on the server energy consumption. Figure \ref{fig:sensorsNumber-server} presents the results of the average server energy consumption when varying the number of sensors from 20 to 500, while Figure @@ -570,8 +571,8 @@ In our case with small and sporadic network traffic, these results show that wit Concerning the IoT part, we include the entire IoT device power consumption. Indeed, in our targeted low-bandwidth IoT application, - the sensor is dedicated to this application. From Table - \ref{tab:wifi-energy}, one can derive that the static power + the sensor is dedicated to this application. From Table 1, one can + derive that the static power consumption of one IoT sensor is around 0.9 Watts. Its dynamic part depends on the transmission frequency. @@ -605,7 +606,10 @@ In our case with small and sporadic network traffic, these results show that wit port bandwidth multiplied by the link utilization and the overall static power consumption of the port. Table \ref{tab:netbidules} summarizes the parameters used in our model, they are taken from - \cite{mahadevan_power_2009}. + \cite{mahadevan_power_2009,Hassidim2013}. These are the parameters + used in our formula to compute the values that we used in the + simulations and that are presented in left part of Table 1. + #+BEGIN_EXPORT latex @@ -651,28 +655,49 @@ In our case with small and sporadic network traffic, these results show that wit The Figure \ref{fig:end-to-end} represents the end-to-end system energy consumption using the model described above while varying - the number of sensors. The values are extracted from the - experiments presented in the previous section. - - Note that, for small-scale systems, the server energy consumption - is dominant compared to the energy consumed by the - sensors. However, since we are using a single server, large-scale sensors deployment lead to an - increasing consumption of energy in the IoT part. On the other side, network energy consumption - is stable regarding the number of sensors since the system use case does not required large data - transfers. Thus, to save energy, we should maximize the number - of sensors handle by each cloud server while keeping reasonable sensors request intervals. + the number of sensors for a transmission interval of 10 + seconds. The values are extracted from the experiments presented in + the previous section. #+BEGIN_EXPORT latex \begin{figure} \centering \hspace{1cm} - \includegraphics[scale=0.4]{plots/final.png} + \includegraphics[scale=0.35]{plots/final.png} \label{fig:end-to-end} \caption{End-to-end network energy consumption using sensors interval of 10s} \end{figure} #+END_EXPORT + Note that, for small-scale systems, with WiFi IoT devices, the IoT + sensor part is dominant in the overall energy consumption. Indeed, + the IoT application induces a very small cost on Cloud and network + infrastructures compared to the IoT device cost. But, our model + assumes that a single VM is handling multiple users (up to 300 + sensors), thus being energy-efficient. Conclusions would be + different with one VM per user in the case of no over-commitment on + the Cloud side. For the network infrastructure, in our case of + low-bandwidth utilization (one data packet every 10 seconds), the + impact is almost negligible. + + Another way of looking at these results is to observe that only for + a high number of sensors (> 300), the power consumption of Cloud and + network parts start to be negligible (few percent). It means that, + if IoT applications handle clients one by one (i.e. one VM per + client), the impact is high on cloud and network part if they have + only few sensors. The energy efficiency is really poor for only few + devices: with 20 IoT sensors, the overall energy cost to handle these + devices is 2.5 times the energy consumption of the IoT devices + themselves. Instead of increasing the number of sensors, which + would result in a higher overall energy consumption, one should + focus on reducing the energy consumption of IoT devices, especially + WiFi devices which are common due to WiFi availability + everywhere. One could also focus on improving the energy cost of + Cloud and network infrastructure for low-bandwidth applications and + few devices. + + * Conclusion #+LaTeX: \label{sec:cl} @@ -694,12 +719,17 @@ we propose an end-to-end energy consumption model. This model provides insights on the hidden part of the iceberg: the impact of IoT devices on the energy consumption of Cloud and network infrastructures. On our use-case, we show that for a given sensor, its -larger energy consumption is on the Cloud part. Consequently, with the +larger energy consumption is on the sensor part. But the impact on the +Cloud and network part is huge when using only few sensors with +low-bandwidth applications. +Consequently, with the IoT exploding growth, it becomes necessary to improve the energy -efficiency of applications hosted on Cloud infrastructures. +efficiency of applications hosted on Cloud infrastructures and of IoT devices. Our future work includes studying other types of IoT wireless -transmission techniques and IoT applications in order to increase the -applicability of our model. +transmission techniques that would be more energy-efficient. We also +plan to study other +IoT applications in order to increase the applicability of our model +and provide advice for increasing the energy-efficiency of IoT infrastructures. @@ -1281,7 +1311,7 @@ applicability of our model. #+RESULTS: [[file:plots/sendInterval-cloud.png]] - + * Emacs settings :noexport: # Local Variables: # eval: (unless (boundp 'org-latex-classes) (setq org-latex-classes nil)) |
