Skip to content
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

In high QPS scenarios, kindling agent uses too much CPU to transfer event between probe and collector #265

Closed
jundizhou opened this issue Jun 23, 2022 · 1 comment

Comments

@jundizhou
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
When the single node QPS is greater than 1W, kindling uses more than 1.5 core CPUs, and it is found through the flame diagram that probe and collector use more CPUs for event transmission and serialization

Describe the solution you'd like
After my test, I found that if we use CGO, we can avoid the consumption of serialization and deserialization。And the transmission consumption is also slightly reduced

I will add my test cases right away

@dxsup
Copy link
Member

dxsup commented Jun 27, 2022

Closed by #264

@dxsup dxsup closed this as completed Jun 27, 2022
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

2 participants