# Integrated SDN-NFV 5G Network Performance and Management-Complexity Evaluation
## 4 Evaluation and Result
### Performance Evaluation
\begin{table}
\begin{tabular}{l c c c c} \hline \hline \multicolumn{1}{c}{**Parameter**} & \multicolumn{1}{c}{**Mean Legacy**} & \multicolumn{1}{c}{**Mean Proposed**} & \multicolumn{1}{c}{**Deviation Standard**} & \multicolumn{1}{c}{**Deviation Standard**} \\  & & & **Legacy** & **Proposed** \\ \hline Server Leaf Input Rate & 7.39 Gbps & 7.58 Gbps & 0.206 & 0.208 \\ Server Leaf Output Rate & 7.33 Gbps & 7.53 Gbps & 0.197 & 0.193 \\ Border Leaf Input Rate & 20.97 Gbps & 22.51 Gbps & 0.502 & 0.750 \\ Border Leaf Output Rate & 9 Gbps & 9.83 Gbps & 0.194 & 0.285 \\ \hline \hline \end{tabular}
\end{table} 
Table 5: Legacy vs. proposed throughput comparison table. Latency  
From the data presented in Figure 8, it can be seen that there is a striking difference between the latency of the legacy and the proposed traffic data. The value of decreasing data traffic latency on the leaf switch server is 12.05 ms to 12.15 ms, as shown in Figure 16. This decrease in data traffic latency value is closely related to the optimization of hops through which data traffic passes, for example, if previously there was traffic data from host-1 to host-2 which turned out to be on one server, the traffic data would be forwarded out of the server to the leaf switch server. This is then reflected to the spine switch, and then returned to the leaf switch server until it returned to the server and host-2. Of course, the flow of data traffic such as this can be simplified by bypassing several data-forwarding mechanisms in the computing system, which in this study was carried out using the DPDK and SR-IOV on the server. With the application of DPDK and SR-IOV, the flow of traffic data between hosts and between servers can occur more simply and optimally to reduce the number of hops when data traffic passes. Optimization is performed by mapping the data traffic (between hosts/servers) with the network computing system that will be applied to the virtualized host/network function. Thus, the flow of data traffic and the networking computing system used is right on the target. The border leaf switch is the same as the explanation in the throughput section where the border leaf switch is the estuary of the server leaf switch, and the border leaf switch manages the outgoing traffic data or north-south traffic. The value of decreasing data traffic latency on the leaf switch server is 16.75 ms to 17.85 ms, as shown in Figure 17. A fairly large impact is also seen in the border leaf switch from the application of the new SDN-NFV architecture and modification of the network computing system on this server, because the number of hops passed by data traffic originating from subscribers (users) will also be reduced as well. From Table 6, we can see the trend of increasing latency values after the implementation of the proposed solution. The latency value of SDN-NFV testing on the border and the leaf switch is influenced by the number of hops and the direction of the data traffic. The latency value on the leaf switch server is smaller than that of the border leaf switch, because data communication on the leaf switch server is limited from host to host on one server, host to host between servers, server to leaf switch, and server to border leaf switch, while the value latency on the border leaf switch has more hops because it also counts the hops to the subscriber in terms of the hops at the very end. However, the focus of this research is the comparison of the latency value of the SDN-NFV combination with SDN alone. On average, we can clearly see that the SDN network has a higher latency value than the SDN-NFV combination. This is because of the use of virtualization technology that can boost server performance in processing data. This means that the SDN-NFV combination can serve data requests from subscribers faster than an SDN alone. The smaller the latency  
Figure 16: Server leaf switch latency—All week comparison. value, the better because it can be faster and can fulfill more subscriber traffic.