On Wed, Nov 4, 2009 at 4:20 AM, Mart Sõmermaa <mrts.py...@gmail.com> wrote: > On Tue, May 12, 2009 at 8:54 AM, Cesare Di Mauro > <cesare.dima...@a-tono.com> wrote: >>> Also, I checked out wpython at head to run Unladen Swallow's >>> benchmarks against it, but it refuses to compile with either gcc 4.0.1 >>> or 4.3.1 on Linux (fails in Python/ast.c). I can send you the build >>> failures off-list, if you're interested. >>> >>> Thanks, >>> Collin Winter >> >> I'm very interested, thanks. That's because I worked only on Windows >> machines, so I definitely need to test and fix it to let it run on any other >> platform. >> >> Cesare > > Re-animating an old discussion -- Cesare, any news on the wpython front? > > I did a checkout from http://wpython.googlecode.com/svn/trunk and > was able to ./configure and make successfully on my 64-bit Linux box > as well as to run the Unladen benchmarks. > > Given svn co http://svn.python.org/projects/python/tags/r261 in py261 > and svn co http://wpython.googlecode.com/svn/trunk in wpy, > > $ python unladen-tests/perf.py -rm --benchmarks=-2to3,all py261/python > wpy/python
Do note that the --track_memory option to perf.py imposes some overhead that interferes with the performance figures. I'd recommend running the benchmarks again without --track_memory. That extra overhead is almost certainly what's causing some of the variability in the results. Collin Winter _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
