Skip to content

CPU usage increases ostensibly with update to grpc 1.66.0 #38259

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

Open
atoulme opened this issue Feb 27, 2025 · 6 comments
Open

CPU usage increases ostensibly with update to grpc 1.66.0 #38259

atoulme opened this issue Feb 27, 2025 · 6 comments

Comments

@atoulme
Copy link
Contributor

atoulme commented Feb 27, 2025

Component(s)

No response

Describe the issue you're reporting

See screenshots and current load tests. https://open-telemetry.github.io/opentelemetry-collector-contrib/benchmarks/loadtests/

I see a 10% increase in CPU usage in load test on update to grpc 1.66.0.

I also see a modest increase in memory usage.

Image Image

This change was introduced with #34978

@atoulme atoulme added the needs triage New item requiring triage label Feb 27, 2025
@atoulme atoulme removed the needs triage New item requiring triage label Mar 8, 2025
@atoulme
Copy link
Contributor Author

atoulme commented Mar 8, 2025

@mx-psi @songy23 you merged the change that caused this increase, please take a look.

@mx-psi
Copy link
Member

mx-psi commented Mar 10, 2025

@atoulme Are we sure this increase has been sustained over time? I am not sure how to look at the full historic data for those benchmarks, but given the fact that this commit does not change any Collector code (just bumps the dependencies) and the time that has passed since the change I would like to make sure this was not fixed in grpc-go/its dependencies since.

@songy23

This comment has been minimized.

@songy23
Copy link
Member

songy23 commented Mar 10, 2025

Also thanks @atoulme for catching and raising this, although I'm more concerned on how to detect this in the future. Right now we only run load tests on mainline commits and it seems already too much (#38446). I assume we don't want to run load tests in every PR, that means we cannot know how a PR impacts performance before merging it. On top of that I don't think there is any alert on the load test numbers and it needs a human to check the graphs from time to time which obviously won't work out in the long run.

@atoulme
Copy link
Contributor Author

atoulme commented Mar 17, 2025

@songy23 please open issues to provide alerts regarding load tests.

@mx-psi please open issues also regarding historical lookback.

What about the issue at hand?

@mx-psi
Copy link
Member

mx-psi commented Mar 17, 2025

@atoulme Pressumably you have been able to have access to the historical data on this, could you clarify how before I file any issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants