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

[Core] Refactor: Optimize client request handling to use two async tasks per client #3263

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

barshaul
Copy link
Collaborator

Reduced the number of async tasks per client from task-per-request to two dedicated tasks:

  1. client_reader_loop: Reads and parses requests from the socket, forwarding them for processing.
  2. request_processor_loop: Manages a FuturesUnordered queue, ensuring efficient request execution.

Issue link

This Pull Request is linked to issue (URL): [REPLACE ME]

Checklist

Before submitting the PR make sure the following are checked:

  • This Pull Request is related to one issue.
  • Commit message has a detailed description of what changed and why.
  • Tests are added or updated.
  • CHANGELOG.md and documentation files are updated.
  • Destination branch is correct - main or release
  • Create merge commit if merging release branch into main, squash otherwise.

… client

Reduced the number of async tasks per client from task-per-request to two dedicated tasks:
  1. `client_reader_loop`: Reads and parses requests from the socket, forwarding them for processing.
  2. `request_processor_loop`: Manages a `FuturesUnordered` queue, ensuring efficient request execution.

Signed-off-by: barshaul <[email protected]>
@barshaul barshaul changed the title Refactor: Optimize client request handling to use two async tasks per client [Core] Refactor: Optimize client request handling to use two async tasks per client Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant