Hi Holger, On Sat, Sep 24, 2005 at 08:21:47AM +0200, holger krekel wrote: > did anyone try to profile the translation process > itself recently? If so what where the results?
I've been spending days on that, with the results that the standard library profile.py is very much broken -- it explodes in mysterious ways or just stop profiling after a few seconds. Michael and me have been polishing a new profiler posted on the CPython SF patch tracker, and I've got preliminary results on translate_pypy. I'll need to run it again now that a few last bugs in the profiler have been fixed. (Also, the profiler doesn't support dumping data to a file at the moment.) The place where translate_pypy spends the largest amount of time is objspace.flow.model.traverse(), which subsequently we again reduced and un-generalized. I guess we could at some point get rid of it completely and replace it with two methods on the graph object, to iterate over blocks or links. A bientot, Armin. _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
