Restructure plots directory

include/04-implementation.md

@@ -464,7 +464,7 @@ The worker nodes have a combined capacity of 136 CPU cores and 1134 GiB memory.
 
 \begin{figure}[ht]
 \centering
-\includegraphics[width=\textwidth]{plots/performance-cost-benchmark-static.pdf}
+\includegraphics[width=\textwidth]{plots/mock-results/performance-cost-benchmark-static.pdf}
 \caption{\label{fig:performance-cost-benchmark-static} Results of scaling benchmark. Scaling setting indicates static number of replicas or autoscaling policy.}
 \end{figure}
 
@@ -495,7 +495,7 @@ This is explained by the fact that with few replicas, the same executor needs to
 
 \begin{figure}[ht]
 \centering
-\includegraphics[width=\textwidth]{plots/config-run-variance-static.pdf}
+\includegraphics[width=\textwidth]{plots/mock-results/config-run-variance-static.pdf}
 \caption{\label{fig:config-run-variance-static} Execution time of individual configuration runs (3 benchmarks, 10 configuration runs per benchmark). Numbers in blue indicate the mean value.}
 \end{figure}
 
@@ -571,7 +571,7 @@ For comparison, the figures also show the previously discussed benchmark results
 
 \begin{figure}[ht]
 \centering
-\includegraphics[width=\textwidth]{plots/performance-cost-benchmark-autoscaling.pdf}
+\includegraphics[width=\textwidth]{plots/mock-results/performance-cost-benchmark-autoscaling.pdf}
 \caption{\label{fig:performance-cost-benchmark-autoscaling} Results of autoscaling benchmark. Scaling setting indicates static number of replicas or autoscaling policy.}
 \end{figure}
 
@@ -604,7 +604,7 @@ Thus, it should be empirically determined and adjusted based on user preferences
 
 \begin{figure}[ht]
 \centering
-\includegraphics[width=\textwidth]{plots/config-run-variance-autoscaling.pdf}
+\includegraphics[width=\textwidth]{plots/mock-results/config-run-variance-autoscaling.pdf}
 \caption{\label{fig:config-run-variance-autoscaling} Execution time of individual configuration runs. Numbers in blue indicate the mean value.}
 \end{figure}