Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JAMES-3737 Ability to execute IMAP workload directly on the event loop #973

Merged
merged 9 commits into from
May 9, 2022

Conversation

chibenwa
Copy link
Contributor

Given that we now have reactive IMAP command execution (non blocking)

If we succeed to do large appends command parsing (buffered to a file thus blocking) asynchronously

Then we could handle the all IMAP workload without context switches.

Experimentally we were able to sensibly

@chibenwa chibenwa force-pushed the JAMES-3737-eventloop branch 2 times, most recently from 653ccf2 to f605986 Compare May 5, 2022 00:03
…ents

 - Reduce counts of parameters
 -Also avoid a double map lookup
This enable executing all IMAP requests on the event loop
Avoids context switches on each IMAP requests
They run on an eventLoop thus are immediately applied
Compress response and activation was sent from
the event loop causing them to be sent and
activated prior earlier responses. This causes
a race condition when several commands are
batched.
STARTTLS response and activation was sent from
the event loop causing them to be sent and
activated prior earlier responses. This causes
a race condition when several commands are
batched.
@chibenwa chibenwa merged commit 169d834 into apache:master May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants