Now in Beta: New Relic RPM Ruby Agent version 2.10. Tell us what you think about the newest capabilities.

20 January 2010 at 1:26 pm | In News, Rails, Support, Testing | Leave a Comment

New Relic, Inc. Today we posted a beta version of our newest Ruby Agent, 2.10, which includes some significant enhancements. We invite you to take it for spin and we’d would appreciate your feedback about the features or any bugs and incompatibilities that you might encounter. Please email your comments to support@newrelic.com.

Installing the Ruby Agent

To install the beta as a plugin, delete any existing RPM plugin in the vendor/plugins area and use this command:

ruby script/plugin install git://github.com/newrelic/rpm.git -r ‘refs/tags/v2.10.2_beta1′

To install the beta as a gem, do the following:

git clone git://github.com/newrelic/rpm.git
cd rpm
git checkout v2.10.2_beta1
rake manifest
rake install

Watch the RPM status blog for updates to the beta:  http://rpmstatus.newrelic.com.

Ruby Agent 2.10 Features

Here’s a short run-down of the new features. You can find a more detailed description on our support site.

  • Instrumentation of methods as if they were web transactions for better visibility into background tasks and and other activities occurring outside of normal controller actions.
  • Additional visibility into Garbage Collection statistics in Ruby Enterprise Edition as well as Ruby versions with the Railsbench GC patches compiled in.
  • Additional visibility into the time a request spends in the queue via the X-REQUEST-ENTRY header, easily inserted into Apache configuration.
  • Application profiling in developer mode that enables RPM to give you a list of profiles to examine for each controller action invoked.
  • Instrumentation to automatically capture Sinatra handlers and show them in the UI as controller actions named according to their URI pattern.
  • Capture of Rack apps and Metals as controller actions for more detailed analysis.
  • CPU metric collection in JRuby, allowing you to determine CPU time spent in every controller action.

We’ve also made some configuration and API changes so be sure to check out the release notes. We look forward to hearing from you.

Tuning the Tuning Tool: Enhancing RPM Performance

29 May 2009 at 4:52 pm | In Did You Know, Performance Tuning, Product Update, Support | Leave a Comment

Picture 5When our developers gather to discuss performance improvements, it sometimes sounds like a discussion in freshman philosophy class about man’s ability to know truth. We use RPM to monitor and tune RPM’s performance. The conversation can get odd as we talk about using our Scalability Analysis tool to improve the performance of the Scalability Analysis tool.

But lately we have been having a lot of those kinds of conversations. This week is the first anniversary of the GA release of RPM. In that year, it has become one of the essential tools for more than 1,800 Rails organizations and is now monitoring more than 27,000 app instances. RPM collects more than 50 Billion data rows per month. In other words it has become a very large scale application. And the growth is accelerating. In just the last 2 months our number of  instances managed has increased about 50%!

Picture 6We have also seen an increase in customer usage of the product.  Most users access RPM with the regular browser UI, but many now also utilize our API to access performance data 24×7 through other programs and devices. So there is constant demand on our servers to retrieve and correlate user performance data.

Since we use RPM to monitor RPM, we watch our Apdex scores very closely. In the past month our scores for responsiveness of RPM have occasionally dropped down as low as .91. (Our target, or “T” is set at 1. That is 1 second. So we have been missing our performance targets at times.) It is probably not noticeable to most customers, but we consider this unacceptable. We keep reminding ourselves that the important part of software-as-a-service is service.

To keep up with this growth and demand we have been adding hardware, tweaking code, and considering every opportunity to optimize our performance. If you sometimes encounter a slow graph or report, we apologize. We think we deliver a great service and provide value to our customers every day. But we also believe in transparency and openness and wanted you to know we are striving to do even better.

New Version of RPM Now Available

30 April 2009 at 4:18 am | In Product Update, RPM in the News, Support, Tutorials | 4 Comments

Tonight New Relic released Version 1.3 of RPM. This version contains new features available for all levels of RPM. The three new features in this release are described below.

Apdex Support

RPM's Apdex PageThis feature is available in all RPM levels. What is Apdex? Its a vendor-neutral, independent standard for measuring your users’ satisfaction with the responsiveness of your application. The standard is published by Apdex Alliance, the organization chartered with the creation and dissemination of the specification for the Apdex standard. Why did we implement Apdex support? So that you and your business managers — the business application owner — can have an agreed upon target for the performance of the application. If they say “the app seems to be slow today,” you can say “but we are actually meeting our Apdex target which you set.” The way Apdex scores work is that you set the target for the response time of your app or for specific transactions (controller actions.) This target is usually something like 1 or 2 seconds. The target is referred to as T. T is the level at which users will be satisfied with performance. RPM takes over from there, continuously scoring your whole app as well as any controller actions you want scored. The scores will appear on the Overview Dashboard and on an Apdex Dashboard. Try using the score. Begin by having a serious conversation with the business team about user satisfaction and show them the Apdex score. Refer to it when you hear those dreaded words “I think the app is slow today.”

Capacity Analysis

RPM's Capacity Analysis ScreenThis feature is in our RPM Gold service. One way to plan for increased user traffic is to increase the number of instances in a host (mongrel or passenger.) Typically more instances, better throughput. But there is a trade off. More instances, more CPU, more memory, bigger hosts. Bigger hosts, bigger hosting invoice each month. This can be especially true in a Cloud deployment, like EC2. Its easy to increase instances and spin up new hosts. But if this increase in capacity is a knee-jerk response to what might be a temporary condition, you could end up with too much capacity and an expensive hosting charge. On the other hand, if you have not configured enough instances, all the tuning in the world won’t improve your throughput. If your queues get too long, your users will see the wait times lengthen. That’s bad. The new Capacity Analysis feature continuously analyzes your instance utilization and shows you vividly whether you are have too many or not enough instances. The page also shows you the ideal instance count so that you can “dial up or dial down” the number of instances. The goal is to find that sweet spot and then recalibrate it as your application and load changes over time. This is a powerful addition to the RPM capability. Its a must have for any application with heavy load and a moderate to large number of  instances. Check out Bayard Carlin’s App Server Provisioning and Tuning article over on RailsLab. He used the Capacity Analysis feature extensively.

Custom Dashboards

A Sample RPM Custom DashboardThis feature is in our RPM Gold service. Ever wanted to create your own RPM dashboard? You know there is all that incredible data collected by RPM. Ever been asked by your business team for a real-time view of the business transactions running through your applications? Now both of these are possible with Custom Dashboards. In minutes, you can create new metrics, select a display widget, add your logo or company name, pick out some meaty business metrics like number of new customer accounts created, purchase transactions, cancellations, or new subscribers, compare the numbers to this time last week, and bang! Show that to the boss and watch him light up. Where did you get this data? This is so cool! The great part is you already have the tool — RPM — and you already have the data. Now with a few minutes of HTML coding, you have a whole new set of flashy dashboards your whole team can use every day. This is big.

Not a Gold customer? Watch this space. We are going to have a very special announcement next week during RailsConf. But don’t wait. Sign up for RPM Gold now and you will get in on our special deal next week.

State of the Stack – A New RoR Benchmarking Report on RailsLab

1 April 2009 at 6:10 pm | In Performance Tuning, Rails, Support | 1 Comment

Banner - Rails Benchmarking ReportNew Relic helps over 1500 Rails organizations monitor and manage their applications. This gives us insight into the application stacks used by developers around the world.

We recently analyzed all of the application instances which use New Relic RPM. We identified the OS, Ruby and Rails versions used and also identified all of the plugins in each stack. The results reveal some interesting information about how quickly the Rails community adopts new versions of Ruby and Rails; about which plugins they find useful; and about the operating systems most commonly used (uh, big surprise, it’s Linux…)

This week we published our results for the first time on RailsLab. The State of the Stack is a report which lists the most commonly used versions of Ruby, Rails, and plugins in actual production applications.

We must be careful to state that the plugin analysis is not a market share report. These lists are also not a complete list as they have been truncated for inclusion in the report.

Compare the benchmarks to your own stack.

Winners of New Relic API Contest Announced

25 March 2009 at 11:54 pm | In Affiliate, Product Update, RPM in the News, Support, Tutorials | 2 Comments

A couple months ago with the introduction of a data API for New Relic RPM, we announced the API Contest to encourage use of the API among our customers. We had many submissions from individuals and from our Affiliates. Our judges evaluated each entry on four criteria – Usefulness to a developer or operations team; Creativity; Ease of implementation; and Use of API features. The judges have evaluated the submissions by individuals and named the four winners. The scoring was remarkably close. Congratulations to all of our contestants. Here are the winners.

David SmithFirst Place: Mac System Bar Status – David Smith
David is with CrossForward a Rails development shop in Virginia. He has won our first place prize of a $1,000 Amazon gift certificate. His submission can be found on GitHub. “I have created a Mac OS X Stats Bar Application that uses the API to keep a constant dashboard of your application’s status in your screen’s corner at all times.” If you are a Mac user, you will find yourself glancing at the RPM status lights all the time. A real time saver.

 

Jesse AndrewsSecond Place: New Relic status in your Firefox browser – Jesse Andrews
Jesse writes on his website Overstimulate.com. He is a contract developer in SF. His submission can be found at his website. “After entering your license key (found in the Accounts tab of your dashboard), your application’s health is checked every minute, showing the traffic lights for your selected app. To change between your applications you can click on the new relic dropdown menu. Hovering on the traffic light gives you more information, clicking on the lights takes you to the overview for your application.”

Luc CasteraThird Place: NewRelic iGoogle Gadget – Luc Castera
Luc Castera was born and raised in Port-au-Prince, Haiti, he now lives in the DC Metropolitan area. He is the co-founder of ShareMeme. “I’ve created an iGoogle Gadget that shows the status of all the applications you have on RPM. You can add the gadget to your page by going to Google. Once you have added the application, put in your NewRelic RPM License key and it should load your ‘lights’. It refreshes the data every minute.”

 

John WiliamsFourth Place: NR Notify – John Williams
John is a developer with Contegix. Contegix, based in St. Louis, MO, provides high-level managed hosting solutions for enterprise applications. You can find John’s submission at the Contegix site. “NR Notify is a simple ruby based notification tool for New Relic RPM. With NR Notify you can add email and SMS notifications to your Ruby on Rails and Merb applications. By using the the New Relic API, NR Notify provides email and SMS notifications based off of your ‘Traffic Light’ settings within New Relic.”

Congratulations to all our winners, and thank you to all of our contestants. We encourage you to try your own hand at developing a creative and useful application of the RPM API.

Note that New Relic does not maintain these applications nor do we support or guarantee them for use with your own data.

Next Page »

Blog at WordPress.com. | Theme: Pool by Borja Fernandez.
Entries and comments feeds.