Hi Anto, On Wednesday 2017-01-18 10:02, Antonio Cuni wrote:
The original goal of capnpy was to be as fast as possible on PyPy. However, if you find that C++ + cppyy is faster, I'd be very interested to know :).
since you wrote the initial data access part yourself way back when, I'd expect you to fix cppyy if it were slower! :) (Only changes I made is to support multiple virtual inheritance and to specialize to make sure the common case is not slowed down by that.) But the only time that I have found where C++/cppyy is faster on PyPy than pure Python is for data member access precisely b/c the C++ structs have fixed offsets, and you seem to have covered that case by specializing. See this report, figure 4: http://conferences.computer.org/pyhpc/2016/papers/5220a027.pdf But, in cppyy, if there is string handling going on, with C-strings being a stand-in for "byte*" (a type that was again voted down, so is not coming soon), there may be spurious copies if not otherwise specialized. Best regards, Wim -- wlavrij...@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
