We setup New Relic in production yesterday. Its awesome! If you're running a rails project of any size, I would say its an indispensable tool.
Here's a brief review:
What it has meant to us:
- Helped us fix 2 new performance problems in 2 hours.
- Helped us identify an intermittent performance problems that we hadn't been able to figure out for the last 3 months (that was mainly because we weren't allowed to increase log level or access apache logs, because of IT bureaucracy. NewRelic allowed us to side-step all of them).
- Easy to setup. All it took was to vendorize a gem and add a yml file.
- The ability to see what action is taking the longest and what partial rendering is taking the longest and what sql is taking the longest is awesome.
- Made for rails
- Pretty graphs. Keeps managers busy for hours. ;-)
- Doesn't seem to make any material impact on the performance of the app.
No visibility into Java code (we run on JRuby in JBoss and have to access some Java code - which is usually the problem). I wonder if there's a way to instrument it so certain calls are visible to New Relic.UPDATE: Yeah, there is a way to see what the Java stuff is doing. It works as advertised, but not as automagically as the Rails logging. Also, we weren't able to get it to log to the same "application". Had to give it a new name.
- Rails only as far as I can tell. It won't work for your Java or .NET project. Sorry!
- Have noticed a couple of stack traces with "new_relic" in them. Need to investigate why.
- newrelic.com was down for a few minutes today. That meant we couldn't stare at the pretty graphs for that time period. Will have to see if uptime is good enough for what we're doing over the next month or so