Add benchmark metrics, with timings and network + memory usage.

Along with a comparison with OfflineIMAP.

1 files changed, 6 insertions, 5 deletions

diff --git a/doc/getting-started.md b/doc/getting-started.md
index 371449d..e20b71d 100644
--- a/doc/getting-started.md
+++ b/doc/getting-started.md
@@ -26,8 +26,8 @@ not*.  Instead, InterIMAP needs an [IMAP4rev1] server on *both* peers
 to synchronize.  This may sound like a severe limitation at first, but by
 seeing both local and remote mail storage though the same “IMAP lens”,
 InterIMAP is able to take advantage of the abstraction layer and
-perform significant optimizations, yielding much faster synchronization.
-(*TODO* link to benchmark.)
+perform significant optimizations, yielding [much faster](benchmark.html)
+synchronization.
 *Note*: InterIMAP uses the [Quick Mailbox Resynchronization][RFC 7162]
 extension for stateful synchronization, hence won't work on IMAP servers
 that don't advertise support for that extension.
@@ -226,8 +226,9 @@ update is requested every minute.  Thanks to the [`QRESYNC`][RFC 7162]
 IMAP extension a status update scales linearly with the number of
 mailboxes (unlike [OfflineIMAP] *not* with the number of messages).  And
 thanks to the `COMPRESS` extension, the typical volume of data exchanged
-is rather small (*TODO* metrics).  You may even want to override the
-default settings and reduce the interval between status updates to 20s:
+[is rather small](benchmark.html#live-sync).  You may even want to
+override the default settings and reduce the interval between status
+updates to 20s:
 
     $ mkdir -p ${XDG_CONFIG_HOME:-~/.config}/systemd/user/interimap.service.d
 <!-- -->
@@ -266,7 +267,7 @@ Other use-cases:
 
 Benchmarks:
 
-:   *TODO*
+:   [Benchmark metrics and comparison](benchmark.html)
 
 Manual