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

Receiving != data sender #224

Closed
LPardue opened this issue Oct 30, 2023 · 2 comments · Fixed by #271
Closed

Receiving != data sender #224

LPardue opened this issue Oct 30, 2023 · 2 comments · Fixed by #271

Comments

@LPardue
Copy link
Member

LPardue commented Oct 30, 2023

From the intro

Similarly, receiving and processing UDP packets can also be CPU intensive, and reducing acknowledgement frequency reduces this cost at a data sender.

I think this should be data receiver?

@mirjak
Copy link
Contributor

mirjak commented Jan 12, 2024

No I believe data sender is correct but I guess the scenarios is not really clear here as this is probably only true if data is only flowing in one direction. In this case the data sender keeps sending the same amount of data independent of the ACK frequency, thus the data receiver has always the same load in receiving UDP packets. However, if the data receiver sends less ACK frames the data sender will receive less UDP packets.

@mirjak
Copy link
Contributor

mirjak commented Jan 12, 2024

I created PR #265. Does it help?

@mirjak mirjak added the has-pr label Jan 12, 2024
LPardue added a commit that referenced this issue Jan 31, 2024
Alternative to #265.

Fixes #224
LPardue added a commit that referenced this issue Jan 31, 2024
Alternative to #265.

Fixes #224
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants