Hi Marko, On Fri, Feb 8, 2013 at 12:22 PM, Marko Tasic <mtasi...@gmail.com> wrote: > What is the status of it ATM, and what is best way to test > and deploy pypy with stm?
The STM project progressed slowly during the last few months. The status right now is: * Most importantly, missing major Garbage Collection cycles, which means pypy-stm slowly but constantly leaks memory. * The JIT integration is not finished; so far pypy-stm can only be compiled without the JIT. * There are also other places where the performance can be improved, probably a lot. * Finally there are a number of usability concerns that we (or mostly Remi) worked on recently. The main issues turn around the idea that, as a user of pypy-stm, you should have a way to get freeback on the process. For example right now, transactions that abort are completely transparent --- to the point that you don't have any way to know that it occurred, apart from "it runs too slowly" if it occurs a lot. You should have a way to get Python tracebacks of aborts if you want to. A similar issue is "inevitable" transactions. A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
