Author: Carl Friedrich Bolz <cfb...@gmx.de> Branch: extradoc Changeset: r5173:4ff712ba945b Date: 2014-04-04 11:51 +0200 http://bitbucket.org/pypy/extradoc/changeset/4ff712ba945b/
Log: more like a profiler at least at first diff --git a/planning/tmdonate2.txt b/planning/tmdonate2.txt --- a/planning/tmdonate2.txt +++ b/planning/tmdonate2.txt @@ -23,10 +23,10 @@ The present proposal is about development of the second half: starting from the various missing low-level optimizations, it will most -importantly focus on developping the Python-facing interface. This +importantly focus on developing the Python-facing interface. This includes both internal things (e.g. do dictionaries need to be more TM-friendly in general?) as well as directly visible things (e.g. some -debugger-like interface to explore common conflicts in a program). It +profiler-like interface to explore common conflicts in a program). It also includes exploring and tweaking some existing libraries to improve their TM-friendliness (e.g. Twisted and Stackless). @@ -315,7 +315,7 @@ feedback about what conflicts we get in these long-running transactions, and where they are produced. A first step will be to implement getting "tracebacks" that point to the places where the most time is lost. This -could be later integrated into some "debugger"-like variant where we can +could be later integrated into some "profiler"-like variant where we can navigate the conflicts, either in a live program or based on data logs. Some of these conflicts can be solved by improving PyPy-TM directly. _______________________________________________ pypy-commit mailing list pypy-commit@python.org https://mail.python.org/mailman/listinfo/pypy-commit
