Rails is a full-stack framework for developing database-backed web applications according to the Model-View-Control pattern. From the Ajax in the view, to the request and response in the controller, to the domain model wrapping the database, Rails gives you a pure-Ruby development environment. To go live, all you need to add is a database and a web server.
Here is a dashboard by Fiveruns that monitors the health of your Rails Applications.
It highlights important metrics for sysadmins and also provides starting points for developers to improve an application’s performance, if necessary.
On the left “Performance” column, users find average global metrics and associated sparkline graphs for the selected time period. The page default is 6 hours but can span a range from 1 to 24 hours. Following any of these metrics takes users to the detailed, interactive metric graphs in Manage.
As a complement, the right “Analytics” column lists the ten slowest actions and the ten most invoked actions of this application. Combined, both tables provide developers valuable indicators where to spend their energy to improve the overall application performance.
Here is an article on how to resolve Rails Performance bottleneck
Developers need to evaluate the priority of performance issues of particular actions. That’s why both average response time and the number of invocations together are important. The below screenshot shows an example scenario where the slowest action of an application is not even listed in the list of most frequently called invoked actions. Here, the index action of the MetricGraphsController is the slowest one. However, it only gets invoked twice during this 6 hour time window. In order to improve overall Rails application performance, engineering resources might be better applied to another actions that get called much more often.