PyPy 1.4: Ouroboros in practice • Hacker News Board

Re: PyPy 1.4: Ouroboros in practice

#11

Post by pquerna » Sat, Nov 27, 2010, 12:47 AM UTC

RyanMcGreal wrote: post #8

>PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython. What still works in CPython but not PyPy?

pyOpenSSL, which means you can't use SSL in twisted :(

Re: PyPy 1.4: Ouroboros in practice

#12

Post by timtadh » Sat, Nov 27, 2010, 2:55 AM UTC

timtadh wrote: post #10

Currently testing a CPU intensive algorithm I need for my current research project. Hoping it will save me some time. When I am done I will post the results! [Edit:] Pretty good so far! ~/stuff/Programming/faultire/src/ hendersont@glycineportable src $ time pypy sleepytree/test_metricspace.py ....... ---------------------------------------------------------------------- Ran 7 tests in 39.621s OK real 0m39.675s user 0…

Another Implementation

    ~/stuff/Programming/sleepytree/
    hendersont@glycineportable sleepytree $ time python test_metricspace.py -v
    test_distance (__main__.TestCompare) ... ok
    test_nondegenercy (__main__.TestCompare) ... ok
    test_symmetry (__main__.TestCompare) ... ok
    test_triangle_inequality (__main__.TestCompare) ... ok
    test_contains (__main__.TestTestNode) ... ok
    test_get (__main__.TestTestNode) ... ok
    test_iter (__main__.TestTestNode) ... ok

    ----------------------------------------------------------------------
    Ran 7 tests in 570.385s

    OK

    real    9m30.451s
    user    9m23.920s
    sys     0m1.730s
    ~/stuff/Programming/sleepytree/
    hendersont@glycineportable sleepytree $ time pypy test_metricspace.py -v
    test_distance (__main__.TestCompare) ... ok
    test_nondegenercy (__main__.TestCompare) ... ok
    test_symmetry (__main__.TestCompare) ... ok
    test_triangle_inequality (__main__.TestCompare) ... ok
    test_contains (__main__.TestTestNode) ... ok
    test_get (__main__.TestTestNode) ... ok
    test_iter (__main__.TestTestNode) ... ok

    ----------------------------------------------------------------------
    Ran 7 tests in 255.339s

    OK

    real    4m15.396s
    user    4m12.990s
    sys     0m0.310s

Re: PyPy 1.4: Ouroboros in practice

#13

Post by santagada » Sat, Nov 27, 2010, 3:00 AM UTC

cool-RR wrote: post #9

RyanMcGreal wrote: post #8

>PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython. What still works in CPython but not PyPy?

wxPython is something I personally miss.

wxPython does work on pypy http://morepypy.blogspot.com/2010/05/running-wxpython-on-top...

Re: PyPy 1.4: Ouroboros in practice

#14

Post by ivank » Sat, Nov 27, 2010, 4:47 AM UTC

RyanMcGreal wrote: post #8

>PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython. What still works in CPython but not PyPy?

pycrypto, gmpy, pyOpenSSL, psycopg2 (fixes in progress, I hear), PyV8, Pyflakes

Re: PyPy 1.4: Ouroboros in practice

#15

Post by bad_user » Sat, Nov 27, 2010, 10:05 AM UTC

timtadh wrote: post #10

Currently testing a CPU intensive algorithm I need for my current research project. Hoping it will save me some time. When I am done I will post the results! [Edit:] Pretty good so far! ~/stuff/Programming/faultire/src/ hendersont@glycineportable src $ time pypy sleepytree/test_metricspace.py ....... ---------------------------------------------------------------------- Ran 7 tests in 39.621s OK real 0m39.675s user 0…

Could you please also run this benchmark compiled with Cython? Thanks,

Re: PyPy 1.4: Ouroboros in practice

#16

Post by hyperbovine » Sat, Nov 27, 2010, 3:17 PM UTC

RyanMcGreal wrote: post #8

>PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython. What still works in CPython but not PyPy?

Anything that relies on C extensions. Numpy is the biggie for me.

Re: PyPy 1.4: Ouroboros in practice

#17

Post by d0mine » Sat, Nov 27, 2010, 3:28 PM UTC

orangecat wrote: post #2

Interesting and promising. PyPy 1.4: >>>> t1 = time.time(); a=[x*x for x in xrange(1000000)]; time.time()-t1 0.38609600067138672 >>>> t1 = time.time(); a=[x*x+math.sin(x/1000000.) for x in xrange(1000000)]; time.time()-t1 0.42182803153991699 Python 2.7: >>> t1 = time.time(); a=[x*x for x in xrange(1000000)]; time.time()-t1 0.25005197525024414 >>> t1 = time.time(); a=[x*x+math.sin(x/1000000.) for x in xrange(1000000)]…

There is something strange with the example.

  $ pypy -mtimeit -s'import math; sin=math.sin' \
      '[x*x+sin(x/1e6) for x in xrange(1000000)]'
  10 loops, best of 3: 156 msec per loop

With no division it is slower (?):

  $ pypy -mtimeit -s'import math; sin=math.sin' \
       '[x*x+sin(x) for x in xrange(1000000)]'
  10 loops, best of 3: 188 msec per loop

CPython shows expected behavior:

  $ python2.7 -mtimeit -s'import math; sin=math.sin' \
    '[x*x+sin(x) for x in xrange(1000000)]'
  10 loops, best of 3: 231 msec per loop

  $ python2.7 -mtimeit -s'import math; sin=math.sin' \
    '[x*x+sin(x/1e6) for x in xrange(1000000)]'
  10 loops, best of 3: 253 msec per loop

CPython is faster for tiny cases:

  $ pypy -mtimeit '[x*x for x in xrange(1000000)]'
  10 loops, best of 3: 126 msec per loop

  $ python2.7 -mtimeit '[x*x for x in xrange(1000000)]'
  10 loops, best of 3: 67.3 msec per loop

  $ pypy -mtimeit '[x*x*x for x in xrange(1000000)]'
  10 loops, best of 3: 123 msec per loop

  $ python2.7 -mtimeit '[x*x*x for x in xrange(1000000)]'
  10 loops, best of 3: 118 msec per loop

Re: PyPy 1.4: Ouroboros in practice

#18

Post by cool-RR » Sat, Nov 27, 2010, 4:36 PM UTC

santagada wrote: post #13

cool-RR wrote: post #9

Earlier quoted context omitted.

wxPython is something I personally miss.

wxPython does work on pypy http://morepypy.blogspot.com/2010/05/running-wxpython-on-top...

That blog post just shows a proof of concept, not official support.

Re: PyPy 1.4: Ouroboros in practice

#19

Post by jbellis » Sat, Nov 27, 2010, 5:23 PM UTC

bad_user wrote: post #15

timtadh wrote: post #10

Currently testing a CPU intensive algorithm I need for my current research project. Hoping it will save me some time. When I am done I will post the results! [Edit:] Pretty good so far! ~/stuff/Programming/faultire/src/ hendersont@glycineportable src $ time pypy sleepytree/test_metricspace.py ....... ---------------------------------------------------------------------- Ran 7 tests in 39.621s OK real 0m39.675s user 0…

Could you please also run this benchmark compiled with Cython? Thanks,

Cython is not (nor is it intended to be) a drop-in Python compiler.

Re: PyPy 1.4: Ouroboros in practice

#20

Post by ivank » Sat, Nov 27, 2010, 5:29 PM UTC

hyperbovine wrote: post #16

RyanMcGreal wrote: post #8

>PyPy is a very compliant Python interpreter, almost a drop-in replacement for CPython. What still works in CPython but not PyPy?

Anything that relies on C extensions. Numpy is the biggie for me.

32-bit pypy 1.4 can compile and run some C extensions; they just have to really well-written (not relying on CPython behavior). It can't find documentation for this, so freenode/#pypy is a good place to get details.