I am playing with newrelic, but there is something bothering me: the
graphs don’t take into account the number of times an action has been
called, it only looks at its average response time.
Well this is a wrong approach. I have an action that takes like 3x more
time than any other action, should I optimize it? According to newrelic,
the answer is obviously yes, but in reality no! Why? Because this action
is a special admin only action used only a few times a day.
I disagree that the approach is wrong per se. Rather, it’s just not what you want. RPM can’t know that any of your actions are “special.” It’s just telling you that, of all the requests that it has seen, some of them are slower than others. I’m not defending RPM because I think it’s the best solution for anyone, I just don’t think that you’re being fair in your judgment. Also, consider making a feature request if it doesn’t do something that you’d like.
However I have noticed that another relatively slow action is my root!
And it is the most often called one! That really surprised me. But the
free edition of newrelic doesn’t enable to profile the action in detail,
and the screenshots are not very clear, so I don’t want to pay $40 for a
I’ve only tried New Relic’s RPM Lite on a staging server so far. Hopefully, I’ll be trying it in production soon. Another performance monitoring tool is offered by FiveRuns [ http://www.fiveruns.com/ ]. I haven’t tried theirs yet.
Using rawk I was able to figure out that most of the time spent on my
root is in rendering, I need to optimize this or it will kill my app.
I’m glad you found something useful.