Erlang Factory SF Bay Area 2012
Microbenchmarks are notoriously bad at predicting overall performance, but running experiments with actual production code using alternative implementations for key algorithms can identify expected performance improvements if the comparisons are executed relative to each other in the same environment. I show how to use YAWS, HTML5 and d3.js to dynamically graph the benchmark performance of erlang code. The goal is to make it easy for a contributor to demonstrate an improvement to your code and convince you to accept a pull request.
Follow us on Twitter @Erlangfactory twitter.com/#!/erlangfactory
Join our group on Linkedin Erlang Factory linkedin.com/groups/Erlang-Factory-2003110?trk=myg_ugrp_ovr