Investigate IMAP folder-open latency (follow-up to #86) #125

Closed
opened 2026-07-02 13:09:47 +00:00 by JMR-dev · 0 comments
JMR-dev commented 2026-07-02 13:09:47 +00:00 (Migrated from github.com)

Follow-up to #86. The mailbox cached-render fix (#123) addresses on-device list rendering cost. The #86 profiling flagged a separate, unmeasured concern: IMAP round-trip latency when opening a folder over the network — distinct from cached rendering and from the prefetch/FetchPolicy work.

Scope

  • Measure the real latency of opening a folder over IMAP (connection setup/reuse, SELECT/EXAMINE round-trips, initial header fetch, TLS handshake), separated from local cache rendering.
  • Determine whether it is a user-perceived problem and, if so, the dominant cause.
  • Propose/implement mitigations if warranted (e.g. connection reuse/pooling, pipelining, optimistic render-from-cache while the network catches up).

Notes

  • Investigation/spike first — like #86, measure before committing to a fix. Use GreenMail for deterministic tests where possible; genuine network latency may need a documented manual measurement.
  • Distinct from #88/#89/#90 (fetch policy) and the backfill work (#94/#95).
Follow-up to #86. The mailbox cached-render fix (#123) addresses on-device **list rendering** cost. The #86 profiling flagged a separate, **unmeasured** concern: IMAP round-trip latency when **opening a folder** over the network — distinct from cached rendering and from the prefetch/FetchPolicy work. ## Scope - Measure the real latency of opening a folder over IMAP (connection setup/reuse, `SELECT`/`EXAMINE` round-trips, initial header fetch, TLS handshake), separated from local cache rendering. - Determine whether it is a user-perceived problem and, if so, the dominant cause. - Propose/implement mitigations if warranted (e.g. connection reuse/pooling, pipelining, optimistic render-from-cache while the network catches up). ## Notes - **Investigation/spike first** — like #86, measure before committing to a fix. Use GreenMail for deterministic tests where possible; genuine network latency may need a documented manual measurement. - Distinct from #88/#89/#90 (fetch policy) and the backfill work (#94/#95).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: JMR-dev/LibreMail#125