TuneUp is FiveRuns’ open source plugin for profiling the performance your Rails and Merb applications. TuneUp is intended to be run locally in your development environment, since the instrumentation returns detailed analysis of a single browser invocation. Bottlenecks can be identified before deployment and before your users experience a performance issue.
Why?
There are some times it may be useful to run TuneUp in production. Perhaps you’d like to share the profiling view across a team. Maybe you’d like to compare the metrics of that same request, against your production database’s configuration, on the actual hardware or under the live platform’s operating system.
All you need to do to activate the TuneUp instrumentation in production is create the following file:
/YOUR/APP/config/tuneup.rb
Containing the following:
Fiveruns::Tuneup.config do |config|
config.environments << :production
end
That’s it. Restart your rails app on the server and it will render the TuneUp instrumentation bar to your local browser. From there, you can toggle it on and off and profile the live server requests remotely.
Why not?
Running TuneUp in production should be done in a closed environment. The instrumentation bar, sequel queries, controller names and other analytics about the code base are displayed. Also, multiple browsers accessing the application concurrently may skew the profiling results.
If you’d like to permanently monitor your servers’ Rails performance in production, check out FiveRuns Manage.
Continued Discussion
No comments have been added yet.