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

UnreliableEvent producing larger payloads than expected. #13

Open
MaximumADHD opened this issue Feb 2, 2024 · 1 comment
Open

UnreliableEvent producing larger payloads than expected. #13

MaximumADHD opened this issue Feb 2, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@MaximumADHD
Copy link

I tried to migrate an UnreliableRemoteEvent over to Red and started seeing oversized payloads.
Normally we're able to fit under the 900 byte limit, but going through Red makes it overflow by 500-600 bytes.

image

Is there anything you guys could do to shrink the overhead of what's being sent over the unreliable wire?

@jackdotink jackdotink self-assigned this Feb 2, 2024
@jackdotink jackdotink added bug Something isn't working enhancement New feature or request and removed bug Something isn't working labels Feb 2, 2024
@jackdotink
Copy link
Member

This behavior happens because Red batches all fires into one remote fire, which can cause it to go over the size limit. Many times this is desirable behavior because it saves a lot of bandwidth, but it can also be undesirable with unreliable remotes in particular because of the size limit.

I think the best way to fix this is to make different channels for unreliables so that they can be batched only when desired. Unfortunately that's difficult and isn't cleanly backwards compatible from what I can tell, so making unreliables not batched is likely the best solution we can implement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants