[erlang-questions] low overhead profiler for erlang?

[Björn-Egil Dahlberg]

There is improvement on the way for eprof (and scaling improvements on 
cprof). There is a dev branch for on github for new breakpoints and an 
improved eprof. Anyone can try it out.

Note that this branch will get rebased and revision will be made but is 
should be stable enough for testing. Some features are just stubs at the 
moment.

git fetch git://github.com/psyeugenic/otp.git wip/call_time_trace_clean

Regards,
Björn-Egil
Erlang/OTP

On 2010-05-03 17:23, mabrek wrote:
> Hello.
>
> Is there a way to do profiling with low overhead?
>
> I tried eprof and fprof, in both cases profiling slowed down my application 10 times. It was able to serve 40 http requests per second without profiling but when I enabled profiling speed dropped down to 4 requests per second.
> It seems that such a big overhead skews results of profiling adding time to frequently called functions.
> I knew that the most time consuming part of my application was database queries (I proved that later by replacing external SQL database with mnesia RAM table), but profiler failed to show it. Frequently called xmerl xml escaping functions were above all in a sorted by accumulated time results.
>
> Regards,
> Anton Lebedevich.
>
> ________________________________________________________________
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:erlang-questions-unsubscribe@REDACTED
>