Blackfire.io vs New Relic: What are the differences?
Developers describe Blackfire.io as "Blackfire Profiler automatically instruments your code to gather data about consumed server resources like memory, CPU time, and I/O". Blackfire achieves a new level of accuracy by aggregating several profile samples and getting rid of non relevant data. Get even deeper and review the interactions with your entire stack (SQL database engines, cache servers, ...). On the other hand, New Relic is detailed as "SaaS Application Performance Management for Ruby, PHP, .Net, Java, Python, and Node.js Apps". New Relic is the all-in-one web application performance tool that lets you see performance from the end user experience, through servers, and down to the line of application code.
Blackfire.io and New Relic can be primarily classified as "Performance Monitoring" tools.
Some of the features offered by Blackfire.io are:
- Profile a page at a mouse click thanks to the Blackfire web browser extension
- Browse through the function calls and identify performance bottlenecks thanks to the Blackfire intuitive UI
- Because Blackfire is only triggered when you profile a request, there is no overhead for other requests
On the other hand, New Relic provides the following key features:
- Performance Data Retention
- Real-User Response Time, Throughput, & Breakdown by Layer
- App Response Time, Throughput, & Breakdown by Component
"Deep insights into PHP request cycle" is the top reason why over 4 developers like Blackfire.io, while over 411 developers mention "Easy setup" as the leading cause for choosing New Relic.
Airbnb, Spotify, and StackShare are some of the popular companies that use New Relic, whereas Blackfire.io is used by Blackfire.io, Showpad, and Basharsoft. New Relic has a broader approval, being mentioned in 3142 company stacks & 575 developers stacks; compared to Blackfire.io, which is listed in 7 company stacks and 4 developer stacks.
What is Blackfire.io?
What is New Relic?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Blackfire.io?
Free Heroku add-on. Not particularly useful for us. Rails profilers tend to do a better job at the app level. And I can never really figure out what’s going on with Heroku by looking at New Relic. I don’t know if we’re just not using New Relic correctly or if it really does just suck for our use case. But I guess some insight is better than none.
How do you know what parts of the workflow need improvement? Measure it. With New Relic in place, we have graphs of our API performance and can directly see if a server or zone is causing trouble, and the impact of our changes. There’s no comparison between a real-time performance graph and “Strange, the site seems slow, I should tail the logs”.
We monitor and troubleshoot our app's performance using New Relic, which gives us a great view into each type of request that hits our servers. It also gives us a nice weekly summary of error rates and response times so that we know how well we've done in the past week.
I'm trying to wring more instrumentation out of New Relic as it pertains to Rack, but for the time being, New Relic is monitoring/alerting uptime and some basic performance metrics.
Just like we care about errors, we care about metrics - especially around performance. You'd be crazy not to use it - and not surprisingly, it's a one-click add-on in Heroku.
Profiling of slow requests. It helps to understand the bootstrapping and the whole requests cycle.