You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, We are struggling with an CPU increasing issue after applying Pinpoint java agent(v2.5.2). Comparing before and after applying agent, over 5% of CPU increase was observed in multiple tests. So we have 2 inqueries as below.
Are there resource usage analysis for Pinpoint java agent?
We've seen Performance Analysis page in Pinpoint document. However it concentrates on performance (TPS), we couldn't find any hints for our issue. We're aware of inevitable CPU increase for applying any APM solutions but we want to see some reports for CPU usage.
Additionally, we tried below options to prevent increasing CPU but options were not effective. Do you have any options to recommend for decreasing CPU load?
Then can I get reports about basic resource overhead without considering applications’ characteristics? We are aware of having challenges to seperate agent’s pure resource usage from application’s total resource usage.
However, if you have any reports like below link (it offers usage data about Datadog agent usage.), please share us.
Hello, We are struggling with an CPU increasing issue after applying Pinpoint java agent(v2.5.2). Comparing before and after applying agent, over 5% of CPU increase was observed in multiple tests. So we have 2 inqueries as below.
Are there resource usage analysis for Pinpoint java agent?
We've seen Performance Analysis page in Pinpoint document. However it concentrates on performance (TPS), we couldn't find any hints for our issue. We're aware of inevitable CPU increase for applying any APM solutions but we want to see some reports for CPU usage.
Additionally, we tried below options to prevent increasing CPU but options were not effective. Do you have any options to recommend for decreasing CPU load?
The text was updated successfully, but these errors were encountered: