On Mon, Jul 23, 2012 at 2:53 PM, Antoine Pitrou <solip...@pitrou.net> wrote:
> On Mon, 23 Jul 2012 17:46:29 -0400 > Brett Cannon <br...@python.org> wrote: > > > > OK. Maciej has always told me that a problem with the Unladen benchmarks > > was that some of them had artificial loop unrolling, etc., so I had > assumed > > you had simply fixed those instances instead of creating entirely new > > benchmarks. > > Is artificial unrolling a real problem or does it simply make > maintenance more difficult? > > Regards > > Antoine. > > > -- > Software development and contracting: http://pro.pitrou.net > > > _______________________________________________ > Speed mailing list > Speed@python.org > http://mail.python.org/mailman/listinfo/speed > The result is that the test a) is totally unrepresentative of real code, b) used to cause it to totally avoid the PyPy JIT, this is no longer true. http://hg.python.org/benchmarks/file/72516165f6ed/performance/bm_call_simple.pyis an example . Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero
_______________________________________________ Speed mailing list Speed@python.org http://mail.python.org/mailman/listinfo/speed
