You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
When sending a UDP statsd message, this library always allocates a fixed 512 ByteBuffer. If the data size exceeds this, copying into this buffer will throw a java.nio.BufferOverflowException.
Something like ByteBuffer.wrap is probably more appropriate.
The text was updated successfully, but these errors were encountered:
Yep, my coworker I think has talked to you on discord, we have a handful of changes we'd like to upstream if possible (some may be more controversial than others) 😸
@andrewhamon thanks for putting in these tickets. I am looking at integrating the metrics into prod for a high throughput service and looked at the code and found concerns and was going to put in tickets, but see you have already found and reported the issues. Another minor area for improvement could be to minimise garbage generation e.g. Using ByteBuffer.allocate in UDPClient.send rather than ByteBuffer.wrap seems suboptimal.
Are you planning to upstream some of the changes that you and your coworker have been working on? It would be really handy to have them
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When sending a UDP statsd message, this library always allocates a fixed 512 ByteBuffer. If the data size exceeds this, copying into this buffer will throw a
java.nio.BufferOverflowException
.Something like ByteBuffer.wrap is probably more appropriate.
The text was updated successfully, but these errors were encountered: