# Enhanced Scalability and Security in Blockchain-Based Transportation Systems for Mass Gatherings
## 4 Results and Findings
### Memory Consumption  
Memory consumption is another important variable that determines a system's ability to handle transaction volumes. The basic initial setting of the proposed system will require approximately 4 GB of memory to support 800 TPS. This is deemed efficient as the system consumes low memory overheads and provides in-check performance. With the inclusion of State Channels, the memory consumption increases to approximately 5 GB, as it must save off-chain states and pre-cache transaction information before they can be verified with certainty. Rollups, which involve configuring off-chain transactions and then submitting them to the main chain, increase memory usage to approximately 6.5 GB, primarily due to the difficulty in storing and verifying transactions in batches. When comparisons are made with reference systems, they tend to exhibit a greater use of memory, particularly when scalability solutions are injected. According to reference [33], \begin{table}
\begin{tabular}{c c c c} \hline \hline
**Scenario** & **CPU Usage (\%)** & **Memory Consumption (GB)** & **Testing Time (Minutes)** \\ \hline Proposed System & 15–18 & 4 & 10 \\ \hline
[33] & 20–25 & 4.5–6.0 & 20 \\ \hline
[34] & 22–26 & 5.0–6.5 & 18 \\ \hline
[35] & 25–30 & 5.0–7.0 & 22 \\ \hline
[36] & 28–32 & 5.5–7.0 & 25 \\ \hline
[37] & 22–25 & 5.0–5.5 & 20 \\ \hline
[38] & 25–28 & 5.0–6.5 & 20 \\ \hline
[39] & 25–30 & 5.0–5.5 & 22 \\ \hline
[40] & 28–32 & 5.5–7.5 & 23 \\ \hline \hline \end{tabular}
\end{table} 
Table 6: CPU Usage, memory consumption, and testing time across all references. the baseline system consumes approximately 4.5 GB of memory, while State Channels increase memory usage to between 5.5 GB and 6 GB, and Rollups increase memory consumption to approximately 6.5 GB. According to reference [34], the minimal configuration consumes approximately 4.5 GB, and the State Channels and Rollups provide an additional 6 GB-7 GB of memory. According to reference [35], the baseline memory consumption is 5 GB-6 GB, and State Channels and Rollups consume at best 7 GB and 8 GB memory, respectively. Although the memory consumption of the proposed system competes favorably with reference models, it is more streamlined even in the case of the Rollup scenario, when other systems are likely to consume a tremendous amount of memory. * Testing Time  
Testing time is a significant measure that indicates the system's capacity to make transactions swiftly and effectively in various settings. The baseline configuration in the proposed system takes about 15 min to reach 800 TPS of testing, which is not excessive considering the required number of transactions. If State Channels are used, the testing time will fall to 12 min, as we will reduce the number of on-chain transactions. The least testing time is experienced with Rollups, which reduces testing time to as short as 10 min at 3500 TPS due to the Rollups' capability to harvest in batches. By comparison, testing usually takes longer in reference systems. For example, [33] indicates that the baseline configuration requires approximately 20 min of testing, whereas State Channels reduce it to 15 min. The time spent on testing in this context increases to 20 to 25 min, as batch transactions require a high volume of transactions. Likewise, the baseline system takes 18 min to test, using State Channels, which reduces the time to 15 min. Rollups, on the other hand, use up to 22 min (source [34]). Other sources, such as 19 and 20, record shorter testing times, with the base configuration taking up to 25 min and Rollups requiring 30 min. The proposed system, therefore, demonstrates its capacity to manage transaction volumes effectively, and its testing times were consistently lower than those of the other reference models, particularly in the Rollup setup. Further, comparing the proposed and reference systems highlights key differences in CPU usage, memory consumption, and testing time.