[erlang-questions] [ANN] Erlang Easy Profiling (eep) provides a way to analyze application performance and call hierarchy

Raimo Niskanen raimo+erlang-questions@REDACTED
Tue Nov 26 14:14:21 CET 2013

On Tue, Nov 26, 2013 at 12:11:11AM +0300, virtan wrote:
> Hi all.
> I just want to present to the community my small project which provides a way
> to analyze performance of your running application and to visualize
> function call hierarchy (with power of kcachegrind as a GUI tool).
> It helped me to find some bottlenecks in our application, would be great
> if it helps someone else.
> https://github.com/virtan/eep

Since EEP in the Erlang world means Erlang Enhancement Proposal
or Erlang Enhancement Process, you might consider another name
for your project, if that was not intentional...

Good name, though.

> Main features:
> 	• no need to modify sources (doesn't need sources at all)
> 	• no need to stop your running system
> 	• start and stop collecting runtime data at arbitrary time
> 	• profile arbitrary module or whole system
> 	• minimal impact on profiled system performance (unlike fprof)
> 	• very informative visualization of time costs and call stacks (kcachegrind)
> 	• ability to export call graphs in dot or image format
> 	• optional process separation
> 	• based on dbg module and built-in low overhead trace ports
> Here is an example what you can get using it:
> https://raw.github.com/virtan/eep/master/doc/sshot1.png
> Permissive MIT license.
> -- 
> virtan / virtan@REDACTED / http://www.virtan.com
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions


/ Raimo Niskanen, Erlang/OTP, Ericsson AB

More information about the erlang-questions mailing list