---------- Forwarded message ---------- From: Isaac Gouy <[email protected]>
Dima Tisnek <dimaqq <at> gmail.com> writes: > > On 20 December 2010 19:21, William ML Leslie > <william.leslie.ttg <at> gmail.com> wrote: > > On 21 December 2010 11:59, Dima Tisnek <dimaqq <at> gmail.com> wrote: > >> More visibility for performance achievements would do > >> good too. > > > > Where are pypy's performance achievements *not* visible, but should be? > > for example http://shootout.alioth.debian.org/ > doesn't say which pypy version is used Oh yes it does - http://shootout.alioth.debian.org/u32/compare.php?lang=pypy#about > what options, doesn't have > performance figures for multithreaded/multicore All the Python multiprocessing programs "Failed" with PyPy - http://shootout.alioth.debian.org/u32/measurements.php?lang=pypy > also benchmarks are kinda small, most of them are not docuemented, and > I couldn't find any info if the same python code was used for cpython > and pypy (both shootout and speed pypy) or interpreter-specific > verions were used, that is each tweaked for best performance given the > known tradeoffs for each implementation. The full source code is shown for all the programs - http://shootout.alioth.debian.org/u32/program.php?test=spectralnorm〈=pypy&id=6 http://shootout.alioth.debian.org/u32/program.php?test=spectralnorm〈=python&id=6 The GZip byte size is shown for each program, in this case 341 for both programs. Maybe the benchmarks game shows more information than you realize. _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
