summaryrefslogtreecommitdiff
path: root/template
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2022-06-15 20:21:23 +0200
committerChristian Grothoff <christian@grothoff.org>2022-06-15 20:21:23 +0200
commitd188ac95f3f7774f65d824e3a848fb499abc8a15 (patch)
tree79c65ad78297ddf53bb25e0dda8ffba1b4814f63 /template
parentdcd75239a255e2af7c688c9d54f029cc875f8695 (diff)
downloadwww-d188ac95f3f7774f65d824e3a848fb499abc8a15.tar.gz
www-d188ac95f3f7774f65d824e3a848fb499abc8a15.tar.bz2
www-d188ac95f3f7774f65d824e3a848fb499abc8a15.zip
-add actual thesis
Diffstat (limited to 'template')
-rw-r--r--template/news/2022-06.html.j220
1 files changed, 10 insertions, 10 deletions
diff --git a/template/news/2022-06.html.j2 b/template/news/2022-06.html.j2
index 30353cb1..701f2acc 100644
--- a/template/news/2022-06.html.j2
+++ b/template/news/2022-06.html.j2
@@ -25,20 +25,20 @@ supported by the Next Generation Internet initiative’s
<a href="https://www.ngi.eu/ngi-projects/fed4fire/">NGI Fed4Fire+</a> program.
<br>
The primary goal of this study was to evaluate the scalability of GNU Taler in a real-world
-scenario. That is, moving away from the loopback system to a distributed network and iden-
-tifying improvement opportunities therein to analyze and improve performance. While the
-basic framework was already known from the previous study, this work focuses on extend-
-ing the framework and making further improvements to GNU Taler. This includes, among
+scenario. That is, moving away from the loopback system to a distributed network and identifying
+improvement opportunities therein to analyze and improve performance. While the
+basic framework was already known from the previous study, this work focuses on extending
+the framework and making further improvements to GNU Taler. This includes, among
other things, the horizontal distribution of the PostgreSQL database.
<br>
We identified and fixed several bottlenecks in the GNU Taler software. We parallelized the
-execution of the cryptographic frontend, leaving the PostgreSQL database as the natural bot-
-tleneck. Here, we optimized queries and modified the schema to enable table partitioning.
-The scalability demonstrated in our experiments shows that Taler is very capable of pro-
-cessing enough transactions per second to be considered an acceptable payment system.
+execution of the cryptographic frontend, leaving the PostgreSQL database as the natural bottleneck.
+Here, we optimized queries and modified the schema to enable table partitioning.
+The scalability demonstrated in our experiments shows that Taler is very capable of processing
+enough transactions per second to be considered an acceptable payment system.
Throughout this work, we were able to increase the performance of Taler by a factor of 95,
-from about 300 to 28.5k transactions per second, showing that Central Bank Digital Curren-
-cies based on Taler would require only a few exchanges per continent.
+from about 300 to 28.5k transactions per second, showing that Central Bank Digital Currencies
+based on Taler would require only a few exchanges per continent.
</p>
<h4>Download links</h4>
<ul>