Use the Profiler
Ruby comes with a code profiler (documentation begins on on page 454). In and of itself, that isn't too surprising, but when you realize that the profiler is written in just about 50 lines of Ruby, that makes for a pretty impressive language.
You can add profiling to your code using the command-line option -r profile, or from within the code usingrequire "profile". For example:
|
require "profile" class Peter def initialize(amt) @value = amt end
def rob(amt) @value -= amt amt end end
class Paul def initialize @value = 0 end
def pay(amt) @value += amt amt end end
peter = Peter.new(1000) paul = Paul.new 1000.times do paul.pay(peter.rob(10)) end |
Run this, and you'll get something like the following.
|
time seconds seconds calls ms/call ms/call name 33.33 0.29 0.29 1 290.00 870.00 Fixnum#times 28.74 0.54 0.25 1000 0.25 0.31 Paul#pay 26.44 0.77 0.23 1000 0.23 0.27 Peter#rob 6.90 0.83 0.06 1000 0.06 0.06 Fixnum#+ 4.60 0.87 0.04 1000 0.04 0.04 Fixnum#- 0.00 0.87 0.00 4 0.00 0.00 Module#method_added 0.00 0.87 0.00 2 0.00 0.00 Class#new 0.00 0.87 0.00 2 0.00 0.00 Class#inherited 0.00 0.87 0.00 1 0.00 0.00 Peter#initialize 0.00 0.87 0.00 1 0.00 0.00 Paul#initialize 0.00 0.87 0.00 1 0.00 870.00 #toplevel |
With the profiler, you can quickly identify and fix bottlenecks. Remember to check the code without the profiler afterward, though---sometimes the slowdown the profiler introduces can mask other problems.
Ruby is a wonderfully transparent and expressive language, but it does not relieve the programmer of the need to apply common sense: creating unnecessary objects, performing unneeded work, and creating generally bloated code are wasteful in any language.
|
Debugger commands
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
