Author: Maciej Fijalkowski <fij...@gmail.com> Branch: extradoc Changeset: r4153:72be6ae2536d Date: 2012-03-18 18:10 +0200 http://bitbucket.org/pypy/extradoc/changeset/72be6ae2536d/
Log: update diff --git a/talk/ep2012/tools/abstract.rst b/talk/ep2012/tools/abstract.rst --- a/talk/ep2012/tools/abstract.rst +++ b/talk/ep2012/tools/abstract.rst @@ -14,6 +14,9 @@ To make matters even more complicated, in JITted VMs, like PyPy, mapping between assembler and high level language, like python, is very unclear and not well known. Writing "good" vs "bad" python (from the JIT perspective), -can make a 20x performance difference. I would like to show current profilers, -their use cases and shortcomings as well as make the case that we need much -better tools to deal with the current situation. +can make a 20x performance difference. + +This talk will cover current profilers available for Pyhon and PyPy, +as well as other tools that can be used to asses performance. I'll also +present in which cases using current tools does not give necessary information +and what kind of tools can address this problem in the future. _______________________________________________ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
