Thanks to all for your answers.
I took some time to think some more about the results and:
For the simple function (which returns 1), CPython roughly takes 1 sec
and pypy 13 secs. IMHO, this case reveals pypy's callback overhead.
For the complex function case, CPython roughly takes 6 secs and
On 11/17/2011 02:56 AM, Alex Gaynor wrote:
> The JIT compiles functions without loops too now, so this should be jitted.
ctypes callbacks still go through the old _rawffi, so it's possible that this
introduces some unneeded overhead.
ciao,
Anto
___
pyp
On Wed, Nov 16, 2011 at 8:24 PM, William ML Leslie <
[email protected]> wrote:
> Ack.
>
> On 17 November 2011 12:23, William ML Leslie
> wrote:
> > On 17 November 2011 12:13, Elefterios Stamatogiannakis
> wrote:
> >> Pypy seems to not jit at all when a (pypy) Python function is called
Ack.
On 17 November 2011 12:23, William ML Leslie
wrote:
> On 17 November 2011 12:13, Elefterios Stamatogiannakis
> wrote:
>> Pypy seems to not jit at all when a (pypy) Python function is called from C.
>
> Calls to native functions must be residualised, as there is no way to
> tell what state
The following code is a lot slower with pypy as compared to CPython. The
code mainly measures the time taken to execute a simple SQLite user
defined function (UDF) and a more complex one, 100 times each.
Execution time for both queries is:
CPython 2.7: 7 sec 489 msec
Pypy nightly build: 28
