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

[Bug] - Process CPU usage spikes when the agent config changed #1577

Open
danipaniii opened this issue Feb 16, 2023 · 0 comments
Open

[Bug] - Process CPU usage spikes when the agent config changed #1577

danipaniii opened this issue Feb 16, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@danipaniii
Copy link
Contributor

Describe the bug
There were reports that when the log-preloading is activated the CPU usage goes up to over 25 % in comparison to 3% when the log-preloading is deactivated.
While investigating this, I found out that whenever the agent config gets changed there is a short CPU usage spike of around 25%.

To Reproduce
Steps to reproduce the behavior:

  1. Start a config server + agent + sample program to attach to
  2. Open e.g. Grafana, Prometheus Graph or other tool to visualize the metrics
  3. After startup and seeing that the overall CPU usage is settling down, change the config
  4. When the config got fetched you can observe the CPU usage spikes.

Expected behavior
Fetching the config, shouldn't result in a CPU usage spike.

Additional context
Unfortunately I don't know whether in the reports it was meant, that the CPU usage stays constantly high after activating the log-preloading or if it was just a short CPU usage spike.

@danipaniii danipaniii added the bug Something isn't working label Feb 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant