Ruby 2.1: Profiling Ruby

Re:Ruby 2.1: Profiling Ruby by gazarsgo on Wednesday December 25, 2013 @02:20AM (#6962479)

Why is line level profiling so non-existent for dynamic languages? Function level just doesn't cut it, esp. w/ the zillions of monkey patches in Ruby.

[ Parent | on HN ]

Re:Ruby 2.1: Profiling Ruby by sams99 on Wednesday December 25, 2013 @08:13AM (#6962934)

Wait, what about stackprof rb-lineprof flamegraph rack-mini-profiler

[ Parent | on HN ]

Re:Ruby 2.1: Profiling Ruby by Mithaldu on Wednesday December 25, 2013 @08:13AM (#6962935)

My theory is that it takes both a certain amount of pressure to create those tools, a certain amount of expertise and a certain amount of tooling available from the language. Due to being old, Perl has all of these and in Devel::NYTProf has a more than excellent profiler that goes beyond line, into statement level. See for example these profiling runs created with it: https://dl.dropboxusercontent.com/u/10190786/ppi_bench.zip

[ Parent | on HN ]

Re:Ruby 2.1: Profiling Ruby by copx on Wednesday December 25, 2013 @04:27AM (#6962667)

>Why is line level profiling so non-existent for dynamic languages?

It isn't. As usual the answer is LuaJIT (sorry, I am a fanboy, got to admit it): http://permalink.gmane.org/gmane.comp.lang.lua.luajit/3413

[ Parent | on HN ]

Re:Ruby 2.1: Profiling Ruby by girvo on Wednesday December 25, 2013 @07:50AM (#6962911)

I was just looking at phpdbg and xdebug yesterday, and they do it, iirc :) so, not impossible, but Ruby does do more stuff dynamically.

[ Parent | on HN ]