summaryrefslogtreecommitdiff
path: root/taler/implementation.tex
diff options
context:
space:
mode:
Diffstat (limited to 'taler/implementation.tex')
-rw-r--r--taler/implementation.tex7
1 files changed, 5 insertions, 2 deletions
diff --git a/taler/implementation.tex b/taler/implementation.tex
index 0413838..e2db92b 100644
--- a/taler/implementation.tex
+++ b/taler/implementation.tex
@@ -1832,7 +1832,10 @@ hardware specifications for our tests:
We used $2048$-bit RSA denomination keys for all of our exchange benchmarks. We
used a development version of the exchange (with git commit hash
-5fbda29b76c24d\dots). PostgreSQL version 10.4 was used as the database.
+5fbda29b76c24d\dots). PostgreSQL version 11.3 was used as the database.
+As our server machines have only slower hard-disk drives instead of faster solid-state drives,
+we ran the benchmarks with an in-memory database.
+
\subsection{Coins Per Transaction}\label{sec:coins-per-transaction}
The transaction rate is an important characteristic of a payment system. Since
@@ -1905,7 +1908,7 @@ correspond to the actual CPU time required for the respective operations, as
the benchmark with one client runs significantly fewer processes/threads than
the number of available CPUs on our machine.
-The benchmark completed in $20.76$ minutes. We obtained the total CPU usage of
+The benchmark completed in $15.10$ minutes on $\texttt{firefly}$. We obtained the total CPU usage of
the benchmark testbed and exchange. The refresh operations are rather slow in comparison
to spends and deposits, as the benchmark with a refresh probability of $0\%$ only took $8.84$
minutes to complete.