Skip to content

perf(jmap): reuse one JMAP client per account within a process - #13824

Open
SebastianKrupinski wants to merge 1 commit into
feat/jmap-2bfrom
perf/jmap-connection-reuse
Open

SebastianKrupinski wants to merge 1 commit into
feat/jmap-2bfrom
perf/jmap-connection-reuse

Conversation

@SebastianKrupinski

@SebastianKrupinski SebastianKrupinski commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Every JMAP operation built a new client, repeating session discovery and the TLS handshake. Pool clients per account and replace them when connection settings or credentials change.
  • SyncJob releases the account's clients so cron runs don't keep connections across accounts.
  • IMAP pooling and job release points for IMAP-only jobs follow separately.

🤖 AI (if applicable)

  • The content of this PR was partly or fully generated using AI (N/A)

@SebastianKrupinski SebastianKrupinski self-assigned this Oct 8, 2026
@SebastianKrupinski
SebastianKrupinski changed the base branch from main to feat/jmap-2b October 8, 2026 14:21
@SebastianKrupinski
SebastianKrupinski added this pull request to stack #13825 October 8, 2026 14:21
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
@SebastianKrupinski
SebastianKrupinski force-pushed the perf/jmap-connection-reuse branch from 960bdca to d023ca2 Compare October 8, 2026 14:28
@SebastianKrupinski SebastianKrupinski changed the title perf(jmap): reuse one client per account within a process perf(jmap): reuse one JMAP client per account within a process Oct 8, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 🏗️ In progress

Development

Successfully merging this pull request may close these issues.

1 participant