Adventures in Optimization.. When a Ruby primitive is the Hog

So you’ve run your code with -rprofile or require ‘profile’

And the answer was IO.each_line

Which is a bit like saying the answer to the Question of Life, the
Universe and Everything is “42”.

a) You’ve used IO.each_line in many places.
b) There is nothing you can do to speed it up.

Enter Carter’s Canny Primitive Profiler…


CUNNING_MIN_CARE = 1 # Only care about stack frames that have been
# at least CUNNING_MIN_CARE times
CUNNING_DEPTH = 2 # Profile base on CUNNING_DEPTH number of
# stack frames of this calls that that
calls… that
# calls Array.each
# Make it -1 if you want the lot.

$f.keys.find_all{|k| $f[k] >= CUNNING_MIN_CARE}.sort_by{|k|
puts “\n\n#{k} >>>#{$f[k]}<<<”

class IO
alias_method :orig_each_line, :each_line
def each_line(&block)
orig_each_line do |l|
i+= 1
$f[caller(1)[0…CUNNING_DEPTH].join("\n")] += i

On exit you can see which invocation of each_line via which path was
the busiest!

Of course, sometimes we don’t actually care about CPU time. The by
several orders of magnitude, the slowest operation in a modern PC is
pulling stuff of the disk.

So how about this variation on the Theme…
class IO
alias_method :orig_read, :read
def read(*arg)
start =
$f[caller(1)[0…CUNNING_DEPTH].join("\n")] += - start

I love Ruby :slight_smile:

John C. Phone : (64)(3) 358 6639
Tait Electronics Fax : (64)(3) 359 4632
PO Box 1645 Christchurch Email : [email protected]
New Zealand

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs