# Scene Equipment Saving and Loading Method for Digital Twin Workshop
## 5 Results and Discussion
### Data Saving and Loading Efficiency
\begin{table}
\begin{tabular}{l c c c c c c c c c c c} \hline \hline
**Content** & **1** & **2** & **3** & **4** & **5** & **6** & **7** & **8** & **9** & **10** & **Average** \\ \hline Saving & & & & & & & & & & & & \\ Boolean & 2 & 2 & 2 & 2 & 2 & 2 & 2 & 2 & 2 & 2 & 2 \\ Byte & 3 & 3 & 3 & 3 & 3 & 3 & 3 & 2 & 2 & 3 & 2.8 \\ Integer & 499 & 500 & 507 & 524 & 498 & 501 & 509 & 501 & 497 & 509 & 504.5 \\ Float & 676 & 691 & 690 & 688 & 688 & 683 & 692 & 689 & 689 & 696 & 688.2 \\ String & 15 & 16 & 16 & 16 & 14 & 16 & 15 & 15 & 15 & 14 & 15.2 \\ \hline Downloading & & & & & & & & & & & \\ Boolean & 26 & 24 & 29 & 24 & 20 & 27 & 26 & 20 & 26 & 25 & 24.7 \\ Byte & 56 & 66 & 57 & 56 & 59 & 51 & 49 & 54 & 48 & 55 & 55.1 \\ Integer & 209 & 205 & 289 & 244 & 288 & 322 & 376 & 292 & 276 & 293 & 279.4 \\ Float & 296 & 199 & 253 & 239 & 230 & 210 & 243 & 284 & 323 & 368 & 264.5 \\ String & 173 & 143 & 156 & 127 & 140 & 133 & 140 & 141 & 155 & 140 & 144.8 \\ \hline Uploading & & & & & & & & & & & \\ Boolean & 1 & 1 & 1 & 1 & 2 & 1 & 1 & 1 & 1 & 1.1 \\ Byte & 28 & 25 & 29 & 29 & 24 & 26 & 23 & 23 & 28 & 25.8 \\ Integer & 213 & 174 & 193 & 177 & 203 & 198 & 205 & 231 & 196 & 215 & 200.5 \\ Float & 372 & 348 & 388 & 314 & 315 & 287 & 301 & 292 & 440 & 396 & 345.3 \\ String & 32 & 37 & 32 & 38 & 43 & 32 & 32 & 30 & 41 & 30 & 34.7 \\ \hline Loading & & & & & & & & & & & \\ Boolean & 3 & 9 & 5 & 7 & 5 & 7 & 7 & 3 & 7 & 8 & 6.1 \\ Byte & 15 & 16 & 5 & 6 & 4 & 3 & 6 & 5 & 4 & 7 & 7.1 \\ Integer & 57 & 60 & 59 & 60 & 62 & 60 & 59 & 60 & 64 & 60 & 60.1 \\ Float & 74 & 78 & 75 & 79 & 78 & 75 & 76 & 77 & 78 & 76 & 76.6 \\ String & 15 & 7 & 9 & 10 & 11 & 11 & 10 & 10 & 11 & 11 & 10.5 \\ \hline \hline \end{tabular} Unit in the table: ms.  
\end{table} 
Table 8: Comparison results of the efficiency for saving and loading basic data type. \begin{table}
\begin{tabular}{l c c c c c c c c c c c} \hline \hline
**Content** & **1** & **2** & **3** & **4** & **5** & **6** & **7** & **8** & **9** & **10** & **Average** \\ \hline Temperature & & & & & & & & & & & & \\ Saving & 488 & 467 & 486 & 487 & 487 & 471 & 489 & 476 & 489 & 467 & 480.7 \\ Loading & 258 & 247 & 252 & 247 & 250 & 245 & 248 & 244 & 247 & 252 & 249.0 \\ \hline Vibration & & & & & & & & & & \\ Saving & 629 & 607 & 605 & 616 & 608 & 632 & 617 & 604 & 606 & 615 & 613.9 \\ Loading & 250 & 270 & 250 & 262 & 256 & 256 & 266 & 260 & 259 & 259 & 258.8 \\ \hline Abrasion & & & & & & & & & & \\ Saving & 1359 & 1358 & 1333 & 1336 & 1362 & 1345 & 1336 & 1338 & 1340 & 1339 & 1344.6 \\ Loading & 408 & 411 & 413 & 403 & 401 & 415 & 406 & 405 & 407 & 415 & 408.4 \\ \hline \hline \end{tabular}  
* Unit in the table: ms.  
\end{table} 
Table 9: Test results for typical composite data saving and loading efficiency tests based on DTWorks architecture. Figure 11: Comparison of saving and loading efficiency results for basic data types. The test results for the two architectures are summarized in Table 11, and a graph comparing their efficiencies is presented in Figure 12.  
As shown in Figure 12, DTWorks continues to demonstrate greater efficiency when saving and loading typical workshop composite data. DTWorks can save millions of complex pieces of data in milliseconds, whereas B/S-based implementations can take seconds. Overall, test results indicate that using DTWorks can increase saving efficiency by 73.6% and loading efficiency by 66.3% for typical complex data types. In conclusion, compared to the DT workshop system based on B/S architecture, the workshop information saving and loading system proposed in this study is more efficient at saving and loading large volumes of data, completing all saving and loading tasks in milliseconds. All operations are multithreaded activities that have no effect on the workshop service software's main thread.