# Performance Optimization of MANET Networks through Routing Protocol Analysis
## 4 Discussion  
The comparison between the AODV and OLSR routing protocols with the test scenarios used in this research shows that the OLSR protocol is only superior in terms of the delay metrics, whereas for other metrics, such as PDR, throughput, packet loss, energy consumption, and routing overhead, the AODV protocol is superior. This is due to the high overhead of the OLSR routing protocol because it is continuously sending routing packets at a certain interval [6]. OLSR has a lower delay than the AODV protocol due to  
Figure 8: Routing overhead results. Figure 7: Average Energy Consumption Results. its nature, which stores routing information on each node, so packets are sent faster [6; 17]. However, this causes OLSR to send many routing packets to control the network topology, causing energy consumption and routing overhead to be very high. This impacts network congestion so that the OLSR routing protocol has a low PDR and throughput. The number of routing packages on the AODV and OLSR routing protocols, based on observation times, is shown in Table 4. In this part of the discussion, we refer to the results at the velocity of 20 m/s, which shows the best results. Other speeds show poor performance, which may be due to the lack of movement of nodes to form new routes after the path is interrupted, resulting in many packets being dropped, thus increasing routing packets because the destination node is not immediately within the range of the source node, which causes a decrease in PDR and throughput. The results presented in Table 5 indicate that the number of routing packets on the AODV protocol does not change after reaching 41. This is due to there being no route changes at 10-200 s. The AODV routing protocol does not send routing packets. Unlike the OLSR routing protocol, although there is no route change on the network, the protocol will still send routing packets for a certain period of time to maintain the routing tables on each node, so the number of generated routing packages increases. Many of these routing packets cause the network traffic to become dense, causing a decrease in the OLSR routing protocols' performance in terms of PDR, throughput, packet loss, delay, and energy consumption. The effect of the parameters RREQ_RETRIES and MAX_RREQ_TIMEOUT on the AODV protocol shows that reducing the value of RREQ_RETRIES and MAX_RREQ_TIMEOUT improves the routing performance, as seen from PDR, throughput, and packet loss. This is because by reducing, in particular, the MAX_RREQ_TIMEOUT value, the route search can be made faster when a route change occurs. A route change occurs once in the test scenario to send a packet from node 0 to node 3. The first route that is formed directly connects node 0 to node 3, which is one hop away. This route lasts until node 0 propagates the RRER message due to node 3, moving away from node 0 and approaching node 2, causing node 3 to be outside the node's reach. \begin{table}
\begin{tabular}{c c c} \hline
**Timestamp (Second)** & **AODV Routing** & **OLSR Routing** \\ \hline
5 & 5 & 15 \\
50 & 41 & 181 \\
100 & 41 & 370 \\
150 & 41 & 576 \\
200 & 41 & 774 \\ \hline \end{tabular}
\end{table} 
Table 4: Total routing packets generated from AODV and OLSR protocols at node speed of 20 m/s. \begin{table}
\begin{tabular}{c c} \hline
**Routing Protocol** & **Time for Forming Routes (Seconds)** \\ \hline AODV 1 & 24.930899 \\ AODV 2 & 23.355387 \\ AODV 3 & 26.801093 \\ AODV 4 & 19.912302 \\ AODV 5 & 20.864071 \\ AODV 6 & 21.907193 \\ AODV 7 & 22.844083 \\ AODV 8 & 23.931910 \\ AODV 9 & 25.913372 \\ AODV 10 & 26.927788 \\ \hline \end{tabular}
\end{table} 
Table 5: Time differences in the formation of routes in AODV protocol variations. In the movement of node 3, previously formed routes cannot be used, so that packets cannot be sent. The route is reformed after node 3 is within reach of node 2. In the formation of the new route, it is necessary to resend the RREQ. The length of time for an RREQ packet depends on the RREQ_RETRIES and MAX_RREQ_TIMEOUT values.