I tried PyPy 1.4 today.

web2py worked out of the box and I am impressed by this. I run some
tests:

TEST1 (web2py)
=====

I run some (sloppy) benchmarks on OSX with ab and I found PyPy to be a
bit lower

no model, no logic, just hello world with trivial template

Cpython: 4ms/request
PyPy: 8ms/request

More complex example (auth, crud, service): the welcome app

Cpython: 68ms/request
PyPy: 89ms/request

I found an occasional "segmentation fault" crash of web2py. I could
not identify the cause.

TEST2 (no web2py, no web server, just loops)
=====

I benchmarked a simple program that performs two nested loops (not
web2py, not web related) and I found:

cPython: 23s
pypy: 15s

Pypy is indeed faster in this case.

TEST 3 (no web2py, just rocket and wsgi hello world)
======

cpython: 0.849ms/request
pypy:   2.109ms/request


Massimo


On Nov 26, 6:51 pm, Phyo Arkar <[email protected]> wrote:
> I think its time try to give web2py on pypy 1.4 a try! its production
> quality they said.
>
> ---------- Forwarded message ----------
> From: Maciej Fijalkowski <[email protected]>
> Date: Fri, 26 Nov 2010 20:23:45 +0200
> Subject: [pypy-dev] PyPy 1.4 released
> To: PyPy Dev <[email protected]>, "<[email protected]>"
>
> <[email protected]>, [email protected]
>
> ===============================
> PyPy 1.4: Ouroboros in practice
> ===============================
>
> We're pleased to announce the 1.4 release of PyPy. This is a major 
> breakthrough
> in our long journey, as PyPy 1.4 is the first PyPy release that can translate
> itself faster than CPython.  Starting today, we are using PyPy more for
> our every-day development.  So may you :) You can download it here:
>
>    http://pypy.org/download.html
>
> What is PyPy
> ============
>
> PyPy is a very compliant Python interpreter, almost a drop-in replacement
> for CPython. It's fast (`pypy 1.4 and cpython 2.6`_ comparison)
>
> Among its new features, this release includes numerous performance 
> improvements
> (which made fast self-hosting possible), a 64-bit JIT backend, as well
> as serious stabilization. As of now, we can consider the 32-bit and 64-bit
> linux versions of PyPy stable enough to run `in production`_.
>
> Numerous speed achievements are described on `our blog`_. Normalized speed
> charts comparing `pypy 1.4 and pypy 1.3`_ as well as `pypy 1.4 and cpython 
> 2.6`_
> are available on benchmark website. For the impatient: yes, we got a lot 
> faster!
>
> More highlights
> ===============
>
> * PyPy's built-in Just-in-Time compiler is fully transparent and
>   automatically generated; it now also has very reasonable memory
>   requirements.  The total memory used by a very complex and
>   long-running process (translating PyPy itself) is within 1.5x to
>   at most 2x the memory needed by CPython, for a speed-up of 2x.
>
> * More compact instances.  All instances are as compact as if
>   they had ``__slots__``.  This can give programs a big gain in
>   memory.  (In the example of translation above, we already have
>   carefully placed ``__slots__``, so there is no extra win.)
>
> * `Virtualenv support`_: now PyPy is fully compatible with
> virtualenv_: note that
>   to use it, you need a recent version of virtualenv (>= 1.5).
>
> * Faster (and JITted) regular expressions - huge boost in speeding up
>   the `re` module.
>
> * Other speed improvements, like JITted calls to functions like map().
>
> .. _virtualenv:http://pypi.python.org/pypi/virtualenv
> .. _`Virtualenv 
> support`:http://morepypy.blogspot.com/2010/08/using-virtualenv-with-pypy.html
> .. _`in 
> production`:http://morepypy.blogspot.com/2010/11/running-large-radio-telescope-so...
> .. _`our blog`:http://morepypy.blogspot.com
> .. _`pypy 1.4 and pypy 
> 1.3`:http://speed.pypy.org/comparison/?exe=1%2B41,1%2B172&ben=1,2,3,4,5,6,...
> .. _`pypy 1.4 and cpython 
> 2.6`:http://speed.pypy.org/comparison/?exe=2%2B35,1%2B172&ben=1,2,3,4,5,6,...
>
> Cheers,
>
> Carl Friedrich Bolz, Antonio Cuni, Maciej Fijalkowski,
> Amaury Forgeot d'Arc, Armin Rigo and the PyPy team
> _______________________________________________
> [email protected]http://codespeak.net/mailman/listinfo/pypy-dev
>
>

Reply via email to