debut param netdev

This commit is contained in:
ORGERIE Anne-Cecile 2019-07-19 10:53:51 +02:00
parent 2d9c7a6a78
commit 5a3e1f62bc

View file

@ -333,7 +333,7 @@ part and the cloud part, as displayed on Figure \ref{fig:parts}.
\centering
\caption{Simulations Energy Parameters}
\label{tab:wifi-energy}
\subtable[Wifi]{
\Subtable[Wifi]{
\begin{tabular}{@{}lr@{}}
Parameter & Value \\ \midrule
Supply Voltage & 3.3V \\
@ -569,6 +569,13 @@ In our case with small and sporadic network traffic, these results show that wit
server belongs to a data center and takes part in the overall
energy drawn to cool the server room.
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
consumption of one IoT sensor is around 0.9 Watts. Its dynamic part
depends on the transmission frequency.
Concerning the sharing of the network costs, for each router, we
consider its aggregate bandwidth (on all the ports), its average
link utilization and the share taken by our IoT application. For a
@ -595,7 +602,26 @@ In our case with small and sporadic network traffic, these results show that wit
Similarly, for each network port, we take the share attributable to
our application: the ratio of our bandwidth utilization over the
port bandwidth multiplied by the link utilization and the overall
static power consumption of the port.
static power consumption of the port. Table \ref{tab:netbidules}
summarizes the parameters used in our model.
#+BEGIN_EXPORT latex
\begin{table}[]
\centering
\caption{Network Devices Parameters}
\label{tab:netbidules}
\begin{tabular}{@{}lr@{}}
Parameter & Value \\ \midrule
Supply Voltage & 3.3V \\
Tx & 0.38A \\
Rx & 0.313A \\
Idle & 0.273A \\ \bottomrule
\end{tabular}}
\end{table}
#+END_EXPORT
For the sharing of the Cloud costs, we take into account the number
of VMs that a server can host, the CPU utilization of a VM and the