From 455dc334e3805cbad0137b694d7def856d0088b0 Mon Sep 17 00:00:00 2001 From: fedir Date: Fri, 16 May 2025 11:51:26 +0200 Subject: [PATCH] txs auto checkin --- evaluation.tex | 65 +++++++++++++++++++++++++++----------------------- 1 file changed, 35 insertions(+), 30 deletions(-) diff --git a/evaluation.tex b/evaluation.tex index 7733a6d..c64f8c1 100644 --- a/evaluation.tex +++ b/evaluation.tex @@ -14,46 +14,51 @@ We tried to asses the quality of ICFS by the following metrics: For performance and usability tests, we used an HP Pavilion Laptop 15-cc563st with an Intel® Core™ i7-7500U processor, a Western Digital WDS250G2B0B WD Blue 3D NAND internal M.2 SATA SSD and 12 GB of DDR4 RAM, running Fedora Linux 42 (Workstation Edition) with Linux 6.14.5-300.fc42.x86\_64 kernel, GNOME 48 desktop environment with Wayland window session. - For additional compatibility tests, a KVM virtual machine running on the same laptop was used. The OS on the virtual machine was Debian GNU/Linux 12 (bookworm) x86\_64 with 6.1.0-27-amd64 kernel, GNOME 43.9 with X11 windowing system. The virtual machine was given 2 CPU cores and 2 GB of RAM. +To assess the qualities of ICFS during regular usage, we have mounted it to a directory pre-filled with files, and attempted to access the files with different software. While trying to simulate common use-case scenarios, we tested the following programs' compatibility and usability with ICFS: + +\begin{itemize} + \item {\TeX}studio. + \item Programming IDE/text editor (Neovim). + \item A web browser (Mozilla Firefox). + \item File manager (GNOME Files, also known as Nautilus). + \item File synchronisation software (Syncthing). + \item Standard command line core utilities (e.g. \verb|ls|, \verb|cd|, \verb|grep|, ...). +\end{itemize} + +We chose these programs not only because of their commonality, but also since they exhibit fairly diverse patterns of filesystem usage that are relevant in practice. + +\iffalse + +For performance testing, special scripts were written, that test the speed of `open` operations. We did not test other operations, since + +\fi + \todo[inline, caption={Complete Evaluation}, author={\textbf{Draft note}}]{The rest of this chapter is \emph{very} incomplete, and only contains a brief and informal talk about the issues I am facing right now. This is not the actual thesis-worthy text. All issues discussed were relevant as of 13.05.2025} -In this chapter presents the method of evaluating the solution is presented, and the found qualities of the solution are discussed. - -Specifically will include: -\begin{itemize} - \item ,,Does the solution actually solve the problem?'' - \item Interoperability with other software: does using this fs break other programs, like whether it interferes with programs using auxiliary files, usability of terminal programs (\verb|grep| is a particularly nasty one for this specific project). - \item Performance and overhead. - \item Security considerations. -\end{itemize} +\section{Security} +\todo[inline, author={\textbf{Draft note}}]{What to even say here?} \section{Usability} -While it is difficult to put an objective score on the usability of any system, we decided to measure the usability of ICFS by the amount +While it is difficult to put an objective score on the ease of use of any system, we measure the usability of ICFS by the amount of dialogues the user has to consciously react to while using the system. -\say{does using this fs break other programs?} -\newline +In our testing we found that most programs' filesystem usage was quite manageable with ICFS. {\TeX}studio and Neovim only required the user to interact with a single dialogue with existing files, and none when creating new files. -\sout{Mostly - no. The biggest issue right now are (ironically) file trackers like tracker-miners. Those are programs that scan the filesystem (e.g. to make file search more efficient). The problem is that the current version of the software does not allow changing the scope of permissions you are giving (e.g. you can't just give permission to access the entire filesystem). - -The solution would be to give an ability to adjust the scope inside the permission dialogue. Everything on the ``backend'' side is ready for this change, but... since I am using zenity it does not easily give me the ability to just add another element to the dialog. Probably a custom dialogue program has to be written, or multiple dialogues would have to be shown(e.g. standard one with Allow/Allow this time/Deny with a ``more options'' button, and then a second zenity dialogue with more detailed configurations) to solve the issue.} - -Now it does not.\newline - -\say{..like whether it interferes with programs using auxiliary files..} -\newline - -No, this issue is solved. Because the programs that use such files are typically the ones that create them, they automatically get the permissions to access them. - -In fact, I am writing this thesis inside of a folder managed by ICFS, and even despite TeX's notorious love for auxiliary files it works just fine.\newline - -\say{..usability of terminal programs (grep is a particularly nasty one for this specific project)} -\newline - -\sout{Yes, this still is an issue. The problem of grep is the same as with file trackers, so I will skip it.} +\begin{figure}[H] + \centering + \begin{subfigure}[b]{0.4\linewidth} + \includegraphics[width=\linewidth]{./images/} + \caption{} + \end{subfigure} + \begin{subfigure}[b]{0.5\linewidth} + \includegraphics[width=\linewidth]{./images/} + \caption{} + \end{subfigure} + \caption{} +\end{figure} This is mostly solved in my experience. It wasn't as annoying to use the terminal programs as I initially expected.