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
Dogstatsd Buffer Size 8k #2638
Comments
8k should be more than enough for anyone! More seriously, it's usually recommended to have the max buffer size set to a small power of 2 (see https://docs.python.org/2/library/socket.html#socket.socket.recv ). That being said there is no reason for it not to be configurable. I'll add this to our backlog. Thanks for the feedback. |
It's not really much considering statsd format is very verbose and a command gets sent for every counter o gauge reported. |
@sschepens Thanks for the feedback, we're looking into making the maximum buffer size in the agent's dogstatsd server configuration. You may also want to try sample rates, which will reduce the number of metrics you submit. See http://docs.datadoghq.com/guides/metrics/#sample-rates |
I see #2804 was closed. Is there still a plan to address this? |
Any updates on this ticket, whether this property is now configurable. We also face similar issue because of this. |
I just enabled |
Is there a reason why Dogstatsd sets buffer size to 8k?
Maximum UDP payload size is actually around 65k and should be ok, I can't find anywhere in statsd's source where they limit buffer size on the server side. The size of messages should be configured by the client and the server should just read the messages.
We're sending lots of metrics from our servers and we wanted to increase the packet size, but packets get cut because Dogstatsd is only reading 8k.
The text was updated successfully, but these errors were encountered: