On 25/11/10 17:46, [email protected] wrote: > yes, but the fast path was disabled (commented out) when updating the branch > with trunk (I needed a few casts in the JIT that were in trunk already, but > not in the branch). It should thus be in addition when it's working again. > (And to be sure, using a float argument makes no difference for the numbers.) > > Myself, I'm just working on functionality right now. A factor of almost 10 > is already good enough to start working on a functional demo of real code, > given that most of our analysis is I/O bound.
wow, if you did not use the fast path, then the 10x factor it's even more impressive :-). I think that yesterday Carl Friedrich added support to cppyy for calling the function through the new JIT-friendly "rlib.libffi" module, so now you should get the "fast-path" performance for most of the calls. Carl, could you post the benchmarks you did please? ciao, Anto _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
