17/66: ccs-2021: Give example authentication throughput.

[Ludovic Courtès]

civodul pushed a commit to branch master
in repository maintenance.

commit 961b7d2a1c5dfa57d463272fb523dda9a70f904a
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Thu May 6 12:12:52 2021 +0200

    ccs-2021: Give example authentication throughput.
---
 doc/ccs-2021/supply-chain.skb | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/doc/ccs-2021/supply-chain.skb b/doc/ccs-2021/supply-chain.skb
index bb4fad4..b306e83 100644
--- a/doc/ccs-2021/supply-chain.skb
+++ b/doc/ccs-2021/supply-chain.skb
@@ -831,7 +831,12 @@ the web of trust, and key expiration and revocation.  
Timestamps in
 OpenPGP signatures and expiry dates are easily forged; what matters in
 our context is the causality of commits: that a signature on a commit is
 valid and authorized.  Likewise, revocation makes little sense in this
-context; what matters is whether the authorization invariant holds.]))
+context; what matters is whether the authorization invariant holds.])
+
+        (p [As an indication, on a recent x86_64 laptop (Intel i7 CPU
+at 2.6 GHz with data stored on a solid state device, SSD), our code
+authenticates between 600 and 700 commits per second, which is fast
+enough to not be detrimental to the user experience.]))
       
       (section :title [Generalization]