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

Eliminate DrasylServerChannel bottleneck #635

Closed
HeikoBornholdt opened this issue Apr 1, 2024 · 1 comment · Fixed by #652
Closed

Eliminate DrasylServerChannel bottleneck #635

HeikoBornholdt opened this issue Apr 1, 2024 · 1 comment · Fixed by #652

Comments

@HeikoBornholdt
Copy link
Member

All messages need to pass DrasylChannel <-> DrasylServerChannel <-> DatagramChannel.
We can have one thread per DrasylChannel (and therefore per peer), and with SO_REUSEPORT, we can also have several DatagramChannels with the respective thread. However, there is only one DrasylServerChannel and only one thread that can process the messages there. This DrasylServerChannel thread represents a performance bottleneck.

We could improve performance by making DraslyChannel process messages directly with DatagramChannel.

@HeikoBornholdt
Copy link
Member Author

@KevinRoebert thoughts on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant