# Non-Face-to-Face P2P (Peer-to-Peer) Real-Time Token Payment Blockchain System
## 5 Experiment and Results
### Performance Testing
#### 5.2.1 Wallet Creation Response Time  
Wallet creation requests are sent to the server and the results are stored in the database. First, the results up to keystore creation are tested. Then, to measure the pure wallet creation time, the IP blocking for DDoS prevention is turned off. For the user10 scenario, assuming a loop of 100 requests with 10 threads, the ramp-up is set to 0, allowing only up to 10 requests per second. For the user20 scenario, assuming a loop of 100 requests with 20 threads, the ramp-up is set to 0, allowing only up to 20 requests per second. For the user50 scenario, assuming a loop of 100 requests with 50 threads, the ramp-up is set to 0, allowing only up to 50 requests per second. The summary of the test results for the three scenarios is shown in Table 13.  
The average response time corresponding to the variation in the number of threads is depicted in Figure 17a. \begin{table}
\begin{tabular}{l c c c c c c c c c c c c} \hline \hline
**Requests** & \multicolumn{4}{c}{**Requests**} & \multicolumn{4}{c}{**Response Times (ms)**} & \multicolumn{4}{c}{**Throughput**} & \multicolumn{2}{c}{**Network (KB/s)**} \\ \cline{2-13}
**Label** &
\begin{tabular}{c} **\#of** \\ **Samples** \\ \end{tabular} & **KO** & **Error\%** & **Average Min** & **Max** & **Median** & **90 th** & **95 th** & **99 th** & **Transaction** & **Receive** & **Send** \\ \hline
**Total** & **8000** & **2** & **0.03\%** & **1222.38** & **11** & **2037** & **1568.00** & **1732.00** & **1767.00** & **1829.00** & **27.98** & **10.37** & **6.07** \\ User10 & 1000 & 0 & 0.00\% & 322.70 & 230 & 552 & 314.50 & 404.00 & 404.00 & 450.96 & 30.66 & 11.35 & 6.59 \\ User20 & 2000 & 0 & 0.00\% & 464.74 & 210 & 912 & 650.50 & 800.95 & 800.95 & 861.00 & 30.52 & 11.30 & 6.56 \\ User50 & 5000 & 2 & 0.04\% & 1632.57 & 11 & 2037 & 1646.00 & 1784.00 & 1784.00 & 1843.00 & 30.47 & 11.30 & 6.54 \\ \hline \hline \end{tabular}
\end{table} 
Table 13: TC1 Response time of keystore creation (without DDoS protection). Figure 16: Experiment environment. Under the same conditions, the results of processing with DDoS blocking turned off are shown in Table 14 and the graphical representation of the results is shown in Figure 17b. The DDoS blocking logic showed an impact of approximately two transactions per second, with 1.61 for user10, 1.9 for User20 and 2.0 for user50 in terms of transactions per second. However, for user50, there was a significant variation in response time. \begin{table}
\begin{tabular}{c c c c c c c c c c c c c c} \hline \hline
**Requests** & \multicolumn{4}{c}{**Requests**} & \multicolumn{4}{c}{**Response Times (ms)**} & \multicolumn{4}{c}{**Throughput**} & \multicolumn{2}{c}{**Network (KB/s)**} \\ \hline \multirow{2}{*}{**Label**} & **\# of** & \multirow{2}{*}{**KQ**} & \multirow{2}{*}{**Error\%**} & \multirow{2}{*}{**Average**} & \multirow{2}{*}{**Min**} & \multirow{2}{*}{**Max**} & \multirow{2}{*}{**Median**} & **90 th** & **95 th** & **99 th** & **Transaction** & \multirow{2}{*}{**Receive**} & \multirow{2}{*}{**Send**} \\  & **Samples** & & & & & & & & & & & & & & & \\ \hline
**Total** & **8000** & **2** & **0.10\%** & **1148.02** & **6** & **1891** & **1483.00** & **1612.00** & **1641.00** & **1700.00** & **170.00** & **6.32** & **3.65** \\ User10 & 1000 & 0 & 0.00\% & 304.58 & 209 & 488 & 296.00 & 360.90 & 390.00 & 431.98 & 32.27 & 11.94 & 6.93 \\ User20 & 2000 & 0 & 0.00\% & 608.69 & 191 & 852 & 617.00 & 711.00 & 737.00 & 786.99 & 32.42 & 12.00 & 6.97 \\ User50 & 5000 & 8 & 0.16\% & 1532.44 & 6 & 1891 & 1544.00 & 1633.00 & 1661.00 & 1712.99 & 32.47 & 12.11 & 6.97 \\ \hline \hline \end{tabular}
\end{table} 
Table 14: TC2 Response time keystore creation (with DDoS protection). Figure 17: TC1 active number of threads vs. response time (**a**) without DDoS protection (**b**) with DDoS protection. (Puple: User10, Red: User20, Yellow: User50).