Diagnosing high CPU use
I'm trying to figure out how I can use New Relic to understand where my CPU use is coming from.
The time consumption page says it can be used for that, however my wall clock time is consumed overwhelmingly by external API calls and database calls (to a DB on a different machine). Correct me if I'm wrong, but time spent waiting for either of those shouldn't be affecting CPU use on my app servers, right?
In that case, is there a useful metric to use?
The time consumption page says it can be used for that, however my wall clock time is consumed overwhelmingly by external API calls and database calls (to a DB on a different machine). Correct me if I'm wrong, but time spent waiting for either of those shouldn't be affecting CPU use on my app servers, right?
In that case, is there a useful metric to use?
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi rmatei,
Your comment about the time consumption page is correct. It finds "wall clock" burners, not necessarily CPU burners. If you have RPM silver or gold, you can use transaction traces to find CPU burners. Each transaction trace shows how much CPU was burned for that transaction. Look for transaction traces for common actions and see which consistently burn high amounts of CPU.
For what it's worth, this use case is one we're investigating a better solution for.
- Jim
Loading Profile...



EMPLOYEE