Skip to content

v0.6.16

@lhaig lhaig tagged this 20 Aug 18:38
The first delivery after a restart took 42-85s, against 63ms once warm,
because the Raft apply maintained per-user search and metadata indexes
inline: the first write paid the cost of opening that user's handles while
the message waited behind it.

Mail and event indexing now runs on a background worker, so a message is
stored and visible immediately and only search catches up fractionally
later. Mailbox listings read from Pebble and are unaffected.

Profile indexing stays inline on purpose, because it writes the shared
system.db that user creation also writes.

Also documents that the 5s passed to the Raft apply is not an upper bound on
the call, sets a SQLite busy timeout, and logs slow index work so a
recurrence reports itself.
Assets 2
Loading