## 4 Experiments and Results
### Average Fragment Creation and Save Time by File Size  
In this section, we add a new element of analysis with respect to the two previous sections; indeed, we analyze the time spent to create and save fragments by considering the different file size scale. Here, we indicate the average time required for creating and saving each fragment for various file sizes. It is an important efficiency indicator that shows how fast the system is at handling smaller parts of data. The shorter the time, the better the system's response to I/O operations, directly influencing overall performance, especially in environments that require high availability and rapid data retrieval operations. Figure 8 depicts the average time required to create fragments as a function of the initial file size. Specifically, the \(x\)-axis represents the size of the initial file to be processed, while the \(y\)-axis shows the processing times in seconds. From the scale of the \(y\)-axis, it is evident that the times are in the order of a few milliseconds, making the impact negligible compared to a cloud solution that adopts this mechanism to enhance the intrinsic security level of the infrastructure, regardless of the security measures chosen by the user for their endpoint. Tables 3-8 complement the information presented in Figure 8, providing a tabular representation of the average, standard deviation, minimum, and maximum execution times for each of the six hardware solutions used in the tests. These metrics are reported for varying sizes of the initial files to be processed. As with Figure 8, the statistics were based on 1000 samples of initial files for each of the file sizes considered. Figure 8: This indicator measures the average time required to create and save a single fragment of a file. Figure 7: This figure measures how long a system takes to completely process and save a file of a certain size, including the division into fragments, the saving of each fragment, and any other process overhead. \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**System 4** & **Mean (s)** & **\(\sigma\) (s)** & **Min (s)** & **Max (s)** \\ \hline
1 kb & 0.0053 & 0.0066 & 0.0009 & 0.0269 \\ \hline
100 kb & 0.0048 & 0.0060 & 0.0016 & 0.0346 \\ \hline
1 mb & 0.0053 & 0.0069 & 0.0015 & 0.0403 \\ \hline
10 mb & 0.0060 & 0.0068 & 0.0019 & 0.0378 \\ \hline
100 mb & 0.0076 & 0.0077 & 0.0025 & 0.1191 \\ \hline \hline \end{tabular}
\end{table} 
Table 6: Analytical results for loading time, including fragmentation, encryption, and saving, in different physical architectures running MuReQua DeSSE with hardware named System 4. \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**System 2** & **Mean (s)** & **\(\sigma\) (s)** & **Min (s)** & **Max (s)** \\ \hline
1 kb & 0.0067 & 0.0078 & 0.0015 & 0.0274 \\ \hline
100 kb & 0.0065 & 0.0066 & 0.0026 & 0.0378 \\ \hline
1 mb & 0.0094 & 0.0087 & 0.0024 & 0.0429 \\ \hline
10 mb & 0.0154 & 0.0108 & 0.0029 & 0.1039 \\ \hline
100 mb & 0.0260 & 0.0111 & 0.0042 & 0.0704 \\ \hline \hline \end{tabular}
\end{table} 
Table 4: Analytical results for loading time, including fragmentation, encryption, and saving, in different physical architectures running MuReQua DeSSE with hardware named System 2. \begin{table}
\begin{tabular}{c c c c c} \hline \hline
**System 1** & **Mean (s)** & **\(\sigma\) (s)** & **Min (s)** & **Max (s)** \\ \hline
1 kb & 0.0120 & 0.0038 & 0.0060 & 0.0269 \\ \hline
100 kb & 0.0268 & 0.0229 & 0.0071 & 0.3790 \\ \hline
1 mb & 0.0278 & 0.0104 & 0.0065 & 0.1900 \\ \hline
10 mb & 0.0317 & 0.0139 & 0.0075 & 0.5645 \\ \hline
100 mb & 0.0365 & 0.0163 & 0.0101 & 0.8321 \\ \hline \hline \end{tabular}
\end{table} 
Table 3: Analytical results for loading time, including fragmentation, encryption, and saving, in different physical architectures running MuReQua DeSSE with hardware named System 1.