-
Notifications
You must be signed in to change notification settings - Fork 174
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
Veneur CPU usage based on metric packets processed per second. #763
Comments
cc @aditya-stripe @antifuchs Does this CPU usage look normal/expected to you? |
That's not expected. Could you share a CPU profile so we can see where that's getting clogged up? |
Cool thanks, am curious how far are we off ? Should it be doing double this or 10x this? profile_120sec.pdf We have flush interval of 30 seconds and run veneur as a sidecar to app in LXC containers. We have the following config for veneur. Also FYI we do run a fork of veneur where we do some metricname parsing and renaming before we flush to signalfx in the sink signalfx.go.
I am attaching the CPU profile for 120 seconds and 300 seconds. |
@aditya-stripe , Sorry before spending more time into investigating bottleneck for CPU usage, am curious to know how much is expected throughput for 1 logical CPU in veneur for metrics consumption via statsd. I noticed similar metric processed throughput per 1 logical CPU when using UDP too. |
Also attaching the UDP profiles (when sending metrics via UDP instead of unix domain socket) |
Hi Team
We are seeing veneur using 1 logical CPU for about 60k metrics processed per second. We are sending stats to Veneur via java datadog client over Unix Domain Socket. Just wanted to know if such usage is expected or if we configured something bad.
Attaching the signalfx charts that show the stats:
veneur.worker.metrics_processed_total
chart:Logical CPU's used by Veneur
chart:The text was updated successfully, but these errors were encountered: