How New Relic Fixes Crappy Code

Why is the application slow? Is it the crappy network or is it the crappy code? Do you blame the IT guy or the developer? If you’re looking at both, you won’t have to blame anyone. You’ll be able to find the problem and fix it, quickly.

Such is the hopeful promise of New Relic, an Application Performance Management Software as a Service solution designed to help you find bottlenecks and run efficiently.

In the above video, Michael Redman, Solution Architect for New Relic, gives us a demo of watching the behavior of a Ruby on Rails application over the network. In the example, you can see that traffic is broken down into separate areas: Ruby, garbage collection, memcache, and external calls, said Redman.

If you have performance issues, those problems will bubble up to the top. If the issue lies in the code, you can drill down and see which specific line of code is slowing down the entire application. You can also see if it’s an anomaly or if it’s happening a lot. If you’re not a developer, you’ll still see what’s wrong and can leave notes for developers, said Redman.

FULL DISCLOSURE: I just began shooting and writing for New Relic’s blog.


2 Responses to “How New Relic Fixes Crappy Code”

November 29, 2012 at 11:52 am, John Pettitt said:

Best system monitoring tool we’ve ever used. We found several nasty latent bugs in the first we we had it live and we cut response time by 50% on a couple of heavily used apps in the fist month.


November 30, 2012 at 8:42 am, Me said:

Wasn’t/Isn’t the developer an “IT guy”?


Post a Comment

Your email address will not be published.