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

[MessageControl] Fixing UDP output and allowing it to store more than one message #315

Merged
merged 2 commits into from
Sep 20, 2024

Conversation

VeithMetro
Copy link
Contributor

Like we discussed on Teams with @sebaszm, there are two major changes:

  1. Making sure that UDP output uses the Convert() as all other Publishers, since it has not been updated up to this point
  2. Allowing to store more than just one message in the _sendBuffer, since the Trigger() call is asynchronous. With Thunder already running, the SendData() method is called on average once every 1-3 calls of the Output() method, but when the framework starts, it can take quite a while before the first buffer "flush" happens (hence 4KB size, since I was still getting an ASSERT with 2KB)

@VeithMetro VeithMetro changed the title [MessageControl] Fixing UDP output and allowing it to store more than one messages [MessageControl] Fixing UDP output and allowing it to store more than one message Sep 16, 2024
@sebaszm
Copy link
Contributor

sebaszm commented Sep 19, 2024

The 4KB value seems arbitrary, but I understand it needs to accommodate asynchronous flushing of the data through the network.

@pwielders pwielders merged commit 216520c into master Sep 20, 2024
28 checks passed
@pwielders pwielders deleted the development/messagecontrol-udp branch September 20, 2024 10:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants