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:
Start a config server + agent + sample program to attach to
Open e.g. Grafana, Prometheus Graph or other tool to visualize the metrics
After startup and seeing that the overall CPU usage is settling down, change the config
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.
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:
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.