From 1a09bd99af38fc7f79f62dc7a8ce907d81219b76 Mon Sep 17 00:00:00 2001 From: fedir Date: Tue, 15 Apr 2025 19:36:51 +0200 Subject: [PATCH] Updated info --- evaluation.tex | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/evaluation.tex b/evaluation.tex index ec99f5d..c49dffc 100644 --- a/evaluation.tex +++ b/evaluation.tex @@ -42,17 +42,9 @@ As for regular terminal programs, I see these possible solutions: \section{Performance} -Performance of ICFS is terrible. Unfortunately, I was unable to make \verb|perf| work with it for some reason, so I don't really know what is slowing operations down. So those are my speculations for what \emph{may} be the bottleneck. - -A lot of it is caused by it's design. For example, ICFS needs to look through procfs to get process creation time, and there is no way of going around this it seems. - -But a lot can also be improved. For example, - -\begin{itemize} - \item sqlite queries can be pre-``compiled'' - \item (I think) more paralellism can be achieved. -\end{itemize} +Performance of ICFS is terrible. \sout{Unfortunately, I was unable to make perf work with it for some reason, so I don't really know what is slowing operations down. So those are my speculations for what \emph{may} be the bottleneck. A lot of it is caused by it's design. For example, ICFS needs to look through procfs to get process creation time, and there is no way of going around this it seems.} +I managed to get the \verb|perf| to work: it showed that almost all time was consumed by libfuse, not my program. My code used something like 0.0001\% of runtime on a pretty heavy test. I am not quite sure what to do, since libfuse is already optimised to smithereens. I guess I will just write how it is and not touch the performance ever again. \section{Limitations} \label{eval:limit}