-
Notifications
You must be signed in to change notification settings - Fork 126
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
[BUG] v0.17.0 CPU usage problem #557
Comments
Hi @Knud3 I'm afraid it would be quite hard to find out problematic commit just by guessing. I see no specific red flags too. So, you would need to pprof it or try to find commit by git bisect. |
I see. Thanks. I try it with pprof and get back with results. |
Same issue here running in K8S go-carbon: v0.17.3/amd64
When I use the sample go-carbon config in the docs I get (0.8% CPU)
|
Hi @wedobetter , |
After updated from v0.16.2 to v0.17.0 CPU usage has skyrocketed. Actually I tried self build version last January and it had that same problem. So problematic commit is somewhere from release v0.16.2 to February.
Usually go-carbon pod used CPU next to nothing, but now hoarding minimum of 3.1 cores. It is running on in its own Kubernetes node with 8 CPU and 64Gb RAM.
Does my config rise any red flags?
go-carbon.conf:
storage-schemas.conf:
storage-aggregation.conf:
carbonapi.yaml:
timeShift.yaml:
Transition from v0.16.2 to v0.17.0:
The text was updated successfully, but these errors were encountered: