diff options
| author | axtloss <axtlos@getcryst.al> | 2024-03-03 00:49:30 +0100 |
|---|---|---|
| committer | axtloss <axtlos@getcryst.al> | 2024-03-03 00:49:30 +0100 |
| commit | 5032249cfba8039fe7a518870a8ce42278a3bf6a (patch) | |
| tree | 2e29461705b29d2bdebe4292df4181cb28a890da /doc/class-assignment/realisierung/verifysetup.tex | |
| parent | fd38eac989e36e3e9d8c8b177c752833e613dcfc (diff) | |
| download | fsverify-5032249cfba8039fe7a518870a8ce42278a3bf6a.tar.gz fsverify-5032249cfba8039fe7a518870a8ce42278a3bf6a.tar.bz2 | |
Finish realisierung
Diffstat (limited to '')
| -rw-r--r-- | doc/class-assignment/realisierung/verifysetup.tex | 21 |
1 files changed, 14 insertions, 7 deletions
diff --git a/doc/class-assignment/realisierung/verifysetup.tex b/doc/class-assignment/realisierung/verifysetup.tex index 9a28b3a..2b79012 100644 --- a/doc/class-assignment/realisierung/verifysetup.tex +++ b/doc/class-assignment/realisierung/verifysetup.tex @@ -9,17 +9,24 @@ Mit dem wechsel zu multithreading ging dies dann runter zu 19 Sekunden mit 12 Th \\ Die Laufzeit von verifysetup verbesserte sich um 33846\% in einer Woche. \begin{verbatim} -10.02.2024: fsverify setup takes 110minutes to complete for 1gb +10.02.2024: +fsverify setup takes 110minutes to complete for 1gb optimizations: none - -12.02.2024: fsverify setup takes 71minutes to complete for 1gb +\end{verbatim} +\begin{verbatim} +12.02.2024: +fsverify setup takes 71minutes to complete for 1gb optimizations: block size 2k, sha1 instead of sha256 - -12.02.2024: fsverify setup takes ~9.54 seconds to complete for 1gb with 12 threads +\end{verbatim} +\begin{verbatim} +12.02.2024: +fsverify setup takes ~9.54 seconds to complete for 1gb with 12 threads optimizations: block size 2k, sha1 instead of sha256, multithreaded, db batch operations - -17.02.2024: fsverify setup takes ~19.50 seconds to complete for 1gb with 12 threads +\end{verbatim} +\begin{verbatim} +17.02.2024: +fsverify setup takes ~19.50 seconds to complete for 1gb with 12 threads optimizations: block size 2k, sha1 instead of sha256, multithreaded, db batch operations unoptimizations: enable database signing, header generation, |