<html><head></head><body><div>Hello,<br> I seem to be having some trouble profiling Erlang. I would really like a simple profiler that counts reductions but fprof gives wall time or CPU time. I am trying to<br>pin point the biggest bottlenecks and what calls them, but fprof is really lacking iMO. Its hard to follow the data it gives, and its hard to build a call tree, it gives some overall information but it also includes things like 'suspend', which confuse the output. <br><br>Anyone know some recommendations for profiling reductions, ideally with a call tree.</div><div class="ydp1938c4a9yahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 13px;"></div></body></html>