-
Notifications
You must be signed in to change notification settings - Fork 20
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
Any reason to set as minimum batch publishing delay 50msec? #332
Comments
@chicco785 there is not a specific reason. Feel free to prepare a PR to reduce the value. I'd say that we can drop down to 10 ms . Thank you. btw there is always the |
@hiimjako I don't recall if there is a reason why we picked send over batchsend |
if you work with @hiimjako I know why, because HA part does not support (yet) the bach send, but only send. :) https://github.com/rabbitmq/rabbitmq-stream-go-client/blob/main/pkg/ha/ha_publisher.go#L112 |
Exactly for this. I think it would be great to have both:
For the first point, why not just do the check that the |
I don't have space now but feel free to propose a PR.
Ok. |
I will do it these days 👍 |
fixed by #333 |
Is your feature request related to a problem? Please describe.
rabbitmq-stream-go-client/pkg/stream/constants.go
Line 107 in baed3d5
in our use case the application work at 20msec frequency, so the idea batch delay should be around that. we can play with batch size, but when some sensors are unreliable, this pops up again, and we need to reconfigure the batch size. setting to 20msec or (16 in the us market), would decrease a lot the lanency for real time processing.
Describe the solution you'd like
if possible, set a batch delay below 50msec.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: