diff options
| author | drbrain <drbrain@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2012-02-23 23:35:21 +0000 |
|---|---|---|
| committer | drbrain <drbrain@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2012-02-23 23:35:21 +0000 |
| commit | 455c23fa015c76dde765b5b417e93ce24bb43ae7 () | |
| tree | 92e5eaed099b058dc5ddc25d97d4b06e3a9d8888 /lib/profiler.rb | |
| parent | b52b1f6a7d1ed9451c067736b7d554fcb41d32ee (diff) | |
Clean whitespace
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34775 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
| -rw-r--r-- | lib/profiler.rb | 36 |
1 files changed, 18 insertions, 18 deletions
@@ -1,51 +1,51 @@ -# Profile provides a way to Profile your Ruby application. -# # Profiling your program is a way of determining which methods are called and # how long each method takes to complete. This way you can detect which # methods are possible bottlenecks. -# # Profiling your program will slow down your execution time considerably, # so activate it only when you need it. Don't confuse benchmarking with # profiling. -# # There are two ways to activate Profiling: -# # == Command line -# # Run your Ruby script with <code>-rprofile</code>: -# # ruby -rprofile example.rb # # If you're profiling an executable in your <code>$PATH</code> you can use # <code>ruby -S</code>: # # ruby -rprofile -S some_executable -# # == From code -# # Just require 'profile': -# # require 'profile' -# # def slow_method # 5000.times do # 9999999999999999*999999999 -# end # end -# # def fast_method # 5000.times do # 9999999999999999+999999999 -# end # end -# # slow_method # fast_method -# # The output in both cases is a report when the execution is over: -# # ruby -rprofile example.rb -# # % cumulative self self total # time seconds seconds calls ms/call ms/call name # 68.42 0.13 0.13 2 65.00 95.00 Integer#times |