Mailman 3 July 2012 - Speed

Re: [Speed] merging PyPy and Python benchmark suite
by Brett Cannon July 24, 2012

July 24, 2012

On Tue, Jul 24, 2012 at 1:14 PM, Alex Gaynor <alex.gaynor(a)gmail.com> wrote: > > > On Tue, Jul 24, 2012 at 10:10 AM, Brett Cannon <brett(a)python.org> wrote: > >> >> >> On Mon, Jul 23, 2012 at 7:34 PM, Maciej Fijalkowski <fijall(a)gmail.com>wrote: >> >>> On Mon, Jul 23, 2012 at 11:46 PM, Brett Cannon <brett(a)python.org> wrote: >>> > >>> > >>> > On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <arigo(a)tunes.org> wrote: >>> >> >>> >> Hi Brett, >>> >> >>> >> On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <brett(a)python.org> >>> wrote: >>> >> > That's what I'm trying to establish; how much have they diverged >>> and if >>> >> > I'm >>> >> > looking in the proper place. >>> >> >>> >> bm_mako.py is not from Unladen Swallow; that's why it is in >>> >> pypy/benchmarks/own/. In case of doubts, check it in the history of >>> >> Hg. The PyPy version was added from virhilo, which seems to be the >>> >> name of his author, on 2010-12-21, and was not changed at all since >>> >> then. >>> > >>> > >>> > 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. >>> >>> No we did not use those benchmarks. Those were mostly completely >>> artificial microbenchmarks (call, call_method etc.). We decided we're >>> not really that interested in microbenchmarks. >>> >>> > >>> >> >>> >> >>> >> Hg tells me that there was no change at all in the 'unladen_swallow' >>> >> subdirectory, apart from 'unladen_swallow/perf.py' and adding some >>> >> __init__.py somewhere. So at least these benchmarks did not receive >>> >> any pypy-specific adapatations. If there are divergences, they come >>> >> from changes done to the unladen-swallow benchmark suite after PyPy >>> >> copied it on 2010-01-15. >>> > >>> > >>> > I know that directory wasn't changed, but I also noticed that some >>> > benchmarks had the same name, which is why I thought they were forked >>> > versions of the same-named Unladen benchmarks. >>> >>> Not if they're in own/ directory. >>> >> >> OK, good to know. I realized I can't copy code wholesale from PyPy's >> benchmark suite as I don't know the code's history and thus if the >> contributor signed Python's contributor agreement. Can the people who are >> familiar with the code help move benchmarks over where the copyright isn't >> in question? >> >> I can at least try to improve the Python 3 situation by doing things like >> pulling in Vinay's py3k port of Django, etc. to fill in gaps. I will also >> try to get the benchmarks to work with a Python 2.7 control and a Python 3 >> "experimental" target for comparing performance since that's what I need >> (or at least be able to run the benchmarks on their own and writing out the >> results for later comparison). >> >> Anything else that should be worked on? >> >> _______________________________________________ >> Speed mailing list >> Speed(a)python.org >> http://mail.python.org/mailman/listinfo/speed >> >> > The important thing is that once a benchmark is in the repo it can *never* > change including all the versions of dependencies, only Python can vary, > otherwise you kill the ability to actually do science with the numbers. > > So, e.g., I wouldn't pull in Vijnay's fork, since that's going to be > utterly obsolete in a few weeks probably, I'd wait to have django on py3k > for that work to all be merged into django itself. > If that's happening in a few weeks then I can wait. But remember my desire is to get benchmark numbers between Python 2.7 and Python 3.3 for my November keynotes so I can't punt indefinitely. -Brett > > 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 > >

1 0

Re: [Speed] merging PyPy and Python benchmark suite
by Antoine Pitrou July 24, 2012

July 24, 2012

On Tue, 24 Jul 2012 13:10:52 -0400 Brett Cannon <brett(a)python.org> wrote: > > OK, good to know. I realized I can't copy code wholesale from PyPy's > benchmark suite as I don't know the code's history and thus if the > contributor signed Python's contributor agreement. Why is that? The benchmark suite isn't included in CPython. As a matter of fact, the current benchmark suite contains code that certainly has not been contributed under the PSF CA (e.g. mako). Regards Antoine. -- Software development and contracting: http://pro.pitrou.net

2 1

Re: [Speed] merging PyPy and Python benchmark suite
by Antoine Pitrou July 24, 2012

July 24, 2012

On Tue, 24 Jul 2012 10:42:15 -0700 Alex Gaynor <alex.gaynor(a)gmail.com> wrote: > > > > PyPy benchmark suite contains stuff from twisted, sympy, mako, tons of > > other libraries. I doubt we can get everyone to sign the contributor > > agreement. > > > > You don't need every individual contributor. Each of those projects has a > copyright holding entity (the DSF, the TSF, etc.), that entity can give the > PSF permission. Twisted doesn't have a "copyright holding entity", and I doubt many other projects do. Regards Antoine. -- Software development and contracting: http://pro.pitrou.net

2 1

Re: [Speed] merging PyPy and Python benchmark suite
by Alex Gaynor July 24, 2012

July 24, 2012

On Tue, Jul 24, 2012 at 10:37 AM, Maciej Fijalkowski <fijall(a)gmail.com>wrote: > On Tue, Jul 24, 2012 at 7:35 PM, Alex Gaynor <alex.gaynor(a)gmail.com> > wrote: > > > > > > On Tue, Jul 24, 2012 at 10:29 AM, Maciej Fijalkowski <fijall(a)gmail.com> > > wrote: > >> > >> On Tue, Jul 24, 2012 at 7:10 PM, Brett Cannon <brett(a)python.org> wrote: > >> > > >> > > >> > On Mon, Jul 23, 2012 at 7:34 PM, Maciej Fijalkowski <fijall(a)gmail.com > > > >> > wrote: > >> >> > >> >> On Mon, Jul 23, 2012 at 11:46 PM, Brett Cannon <brett(a)python.org> > >> >> wrote: > >> >> > > >> >> > > >> >> > On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <arigo(a)tunes.org> > wrote: > >> >> >> > >> >> >> Hi Brett, > >> >> >> > >> >> >> On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <brett(a)python.org> > >> >> >> wrote: > >> >> >> > That's what I'm trying to establish; how much have they diverged > >> >> >> > and > >> >> >> > if > >> >> >> > I'm > >> >> >> > looking in the proper place. > >> >> >> > >> >> >> bm_mako.py is not from Unladen Swallow; that's why it is in > >> >> >> pypy/benchmarks/own/. In case of doubts, check it in the history > of > >> >> >> Hg. The PyPy version was added from virhilo, which seems to be > the > >> >> >> name of his author, on 2010-12-21, and was not changed at all > since > >> >> >> then. > >> >> > > >> >> > > >> >> > 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. > >> >> > >> >> No we did not use those benchmarks. Those were mostly completely > >> >> artificial microbenchmarks (call, call_method etc.). We decided we're > >> >> not really that interested in microbenchmarks. > >> >> > >> >> > > >> >> >> > >> >> >> > >> >> >> Hg tells me that there was no change at all in the > 'unladen_swallow' > >> >> >> subdirectory, apart from 'unladen_swallow/perf.py' and adding some > >> >> >> __init__.py somewhere. So at least these benchmarks did not > receive > >> >> >> any pypy-specific adapatations. If there are divergences, they > come > >> >> >> from changes done to the unladen-swallow benchmark suite after > PyPy > >> >> >> copied it on 2010-01-15. > >> >> > > >> >> > > >> >> > I know that directory wasn't changed, but I also noticed that some > >> >> > benchmarks had the same name, which is why I thought they were > forked > >> >> > versions of the same-named Unladen benchmarks. > >> >> > >> >> Not if they're in own/ directory. > >> > > >> > > >> > OK, good to know. I realized I can't copy code wholesale from PyPy's > >> > benchmark suite as I don't know the code's history and thus if the > >> > contributor signed Python's contributor agreement. Can the people who > >> > are > >> > familiar with the code help move benchmarks over where the copyright > >> > isn't > >> > in question? > >> > > >> > >> Can we find a home for benchmarks where we don't need everyone to sign > >> the copyright agreement? > >> > >> Cheers, > >> fijal > >> > >> _______________________________________________ > >> Speed mailing list > >> Speed(a)python.org > >> http://mail.python.org/mailman/listinfo/speed > > > > > > It seems totally reasonable for them to be official and be under the PSF > > license, and have copyright agreements signed. > > > > 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 > > > > PyPy benchmark suite contains stuff from twisted, sympy, mako, tons of > other libraries. I doubt we can get everyone to sign the contributor > agreement. > You don't need every individual contributor. Each of those projects has a copyright holding entity (the DSF, the TSF, etc.), that entity can give the PSF permission. 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

1 0

Re: [Speed] merging PyPy and Python benchmark suite
by Maciej Fijalkowski July 24, 2012

July 24, 2012

On Tue, Jul 24, 2012 at 7:35 PM, Alex Gaynor <alex.gaynor(a)gmail.com> wrote: > > > On Tue, Jul 24, 2012 at 10:29 AM, Maciej Fijalkowski <fijall(a)gmail.com> > wrote: >> >> On Tue, Jul 24, 2012 at 7:10 PM, Brett Cannon <brett(a)python.org> wrote: >> > >> > >> > On Mon, Jul 23, 2012 at 7:34 PM, Maciej Fijalkowski <fijall(a)gmail.com> >> > wrote: >> >> >> >> On Mon, Jul 23, 2012 at 11:46 PM, Brett Cannon <brett(a)python.org> >> >> wrote: >> >> > >> >> > >> >> > On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <arigo(a)tunes.org> wrote: >> >> >> >> >> >> Hi Brett, >> >> >> >> >> >> On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <brett(a)python.org> >> >> >> wrote: >> >> >> > That's what I'm trying to establish; how much have they diverged >> >> >> > and >> >> >> > if >> >> >> > I'm >> >> >> > looking in the proper place. >> >> >> >> >> >> bm_mako.py is not from Unladen Swallow; that's why it is in >> >> >> pypy/benchmarks/own/. In case of doubts, check it in the history of >> >> >> Hg. The PyPy version was added from virhilo, which seems to be the >> >> >> name of his author, on 2010-12-21, and was not changed at all since >> >> >> then. >> >> > >> >> > >> >> > 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. >> >> >> >> No we did not use those benchmarks. Those were mostly completely >> >> artificial microbenchmarks (call, call_method etc.). We decided we're >> >> not really that interested in microbenchmarks. >> >> >> >> > >> >> >> >> >> >> >> >> >> Hg tells me that there was no change at all in the 'unladen_swallow' >> >> >> subdirectory, apart from 'unladen_swallow/perf.py' and adding some >> >> >> __init__.py somewhere. So at least these benchmarks did not receive >> >> >> any pypy-specific adapatations. If there are divergences, they come >> >> >> from changes done to the unladen-swallow benchmark suite after PyPy >> >> >> copied it on 2010-01-15. >> >> > >> >> > >> >> > I know that directory wasn't changed, but I also noticed that some >> >> > benchmarks had the same name, which is why I thought they were forked >> >> > versions of the same-named Unladen benchmarks. >> >> >> >> Not if they're in own/ directory. >> > >> > >> > OK, good to know. I realized I can't copy code wholesale from PyPy's >> > benchmark suite as I don't know the code's history and thus if the >> > contributor signed Python's contributor agreement. Can the people who >> > are >> > familiar with the code help move benchmarks over where the copyright >> > isn't >> > in question? >> > >> >> Can we find a home for benchmarks where we don't need everyone to sign >> the copyright agreement? >> >> Cheers, >> fijal >> >> _______________________________________________ >> Speed mailing list >> Speed(a)python.org >> http://mail.python.org/mailman/listinfo/speed > > > It seems totally reasonable for them to be official and be under the PSF > license, and have copyright agreements signed. > > 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 > PyPy benchmark suite contains stuff from twisted, sympy, mako, tons of other libraries. I doubt we can get everyone to sign the contributor agreement.

1 0

Re: [Speed] merging PyPy and Python benchmark suite
by Alex Gaynor July 24, 2012

July 24, 2012

On Tue, Jul 24, 2012 at 10:29 AM, Maciej Fijalkowski <fijall(a)gmail.com>wrote: > On Tue, Jul 24, 2012 at 7:10 PM, Brett Cannon <brett(a)python.org> wrote: > > > > > > On Mon, Jul 23, 2012 at 7:34 PM, Maciej Fijalkowski <fijall(a)gmail.com> > > wrote: > >> > >> On Mon, Jul 23, 2012 at 11:46 PM, Brett Cannon <brett(a)python.org> > wrote: > >> > > >> > > >> > On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <arigo(a)tunes.org> wrote: > >> >> > >> >> Hi Brett, > >> >> > >> >> On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <brett(a)python.org> > >> >> wrote: > >> >> > That's what I'm trying to establish; how much have they diverged > and > >> >> > if > >> >> > I'm > >> >> > looking in the proper place. > >> >> > >> >> bm_mako.py is not from Unladen Swallow; that's why it is in > >> >> pypy/benchmarks/own/. In case of doubts, check it in the history of > >> >> Hg. The PyPy version was added from virhilo, which seems to be the > >> >> name of his author, on 2010-12-21, and was not changed at all since > >> >> then. > >> > > >> > > >> > 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. > >> > >> No we did not use those benchmarks. Those were mostly completely > >> artificial microbenchmarks (call, call_method etc.). We decided we're > >> not really that interested in microbenchmarks. > >> > >> > > >> >> > >> >> > >> >> Hg tells me that there was no change at all in the 'unladen_swallow' > >> >> subdirectory, apart from 'unladen_swallow/perf.py' and adding some > >> >> __init__.py somewhere. So at least these benchmarks did not receive > >> >> any pypy-specific adapatations. If there are divergences, they come > >> >> from changes done to the unladen-swallow benchmark suite after PyPy > >> >> copied it on 2010-01-15. > >> > > >> > > >> > I know that directory wasn't changed, but I also noticed that some > >> > benchmarks had the same name, which is why I thought they were forked > >> > versions of the same-named Unladen benchmarks. > >> > >> Not if they're in own/ directory. > > > > > > OK, good to know. I realized I can't copy code wholesale from PyPy's > > benchmark suite as I don't know the code's history and thus if the > > contributor signed Python's contributor agreement. Can the people who are > > familiar with the code help move benchmarks over where the copyright > isn't > > in question? > > > > Can we find a home for benchmarks where we don't need everyone to sign > the copyright agreement? > > Cheers, > fijal > _______________________________________________ > Speed mailing list > Speed(a)python.org > http://mail.python.org/mailman/listinfo/speed > It seems totally reasonable for them to be official and be under the PSF license, and have copyright agreements signed. 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

1 0

Re: [Speed] merging PyPy and Python benchmark suite
by Maciej Fijalkowski July 24, 2012

July 24, 2012

On Tue, Jul 24, 2012 at 7:10 PM, Brett Cannon <brett(a)python.org> wrote: > > > On Mon, Jul 23, 2012 at 7:34 PM, Maciej Fijalkowski <fijall(a)gmail.com> > wrote: >> >> On Mon, Jul 23, 2012 at 11:46 PM, Brett Cannon <brett(a)python.org> wrote: >> > >> > >> > On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <arigo(a)tunes.org> wrote: >> >> >> >> Hi Brett, >> >> >> >> On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <brett(a)python.org> >> >> wrote: >> >> > That's what I'm trying to establish; how much have they diverged and >> >> > if >> >> > I'm >> >> > looking in the proper place. >> >> >> >> bm_mako.py is not from Unladen Swallow; that's why it is in >> >> pypy/benchmarks/own/. In case of doubts, check it in the history of >> >> Hg. The PyPy version was added from virhilo, which seems to be the >> >> name of his author, on 2010-12-21, and was not changed at all since >> >> then. >> > >> > >> > 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. >> >> No we did not use those benchmarks. Those were mostly completely >> artificial microbenchmarks (call, call_method etc.). We decided we're >> not really that interested in microbenchmarks. >> >> > >> >> >> >> >> >> Hg tells me that there was no change at all in the 'unladen_swallow' >> >> subdirectory, apart from 'unladen_swallow/perf.py' and adding some >> >> __init__.py somewhere. So at least these benchmarks did not receive >> >> any pypy-specific adapatations. If there are divergences, they come >> >> from changes done to the unladen-swallow benchmark suite after PyPy >> >> copied it on 2010-01-15. >> > >> > >> > I know that directory wasn't changed, but I also noticed that some >> > benchmarks had the same name, which is why I thought they were forked >> > versions of the same-named Unladen benchmarks. >> >> Not if they're in own/ directory. > > > OK, good to know. I realized I can't copy code wholesale from PyPy's > benchmark suite as I don't know the code's history and thus if the > contributor signed Python's contributor agreement. Can the people who are > familiar with the code help move benchmarks over where the copyright isn't > in question? > Can we find a home for benchmarks where we don't need everyone to sign the copyright agreement? Cheers, fijal

1 0

Re: [Speed] merging PyPy and Python benchmark suite
by Alex Gaynor July 24, 2012

July 24, 2012

On Tue, Jul 24, 2012 at 10:10 AM, Brett Cannon <brett(a)python.org> wrote: > > > On Mon, Jul 23, 2012 at 7:34 PM, Maciej Fijalkowski <fijall(a)gmail.com>wrote: > >> On Mon, Jul 23, 2012 at 11:46 PM, Brett Cannon <brett(a)python.org> wrote: >> > >> > >> > On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <arigo(a)tunes.org> wrote: >> >> >> >> Hi Brett, >> >> >> >> On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <brett(a)python.org> >> wrote: >> >> > That's what I'm trying to establish; how much have they diverged and >> if >> >> > I'm >> >> > looking in the proper place. >> >> >> >> bm_mako.py is not from Unladen Swallow; that's why it is in >> >> pypy/benchmarks/own/. In case of doubts, check it in the history of >> >> Hg. The PyPy version was added from virhilo, which seems to be the >> >> name of his author, on 2010-12-21, and was not changed at all since >> >> then. >> > >> > >> > 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. >> >> No we did not use those benchmarks. Those were mostly completely >> artificial microbenchmarks (call, call_method etc.). We decided we're >> not really that interested in microbenchmarks. >> >> > >> >> >> >> >> >> Hg tells me that there was no change at all in the 'unladen_swallow' >> >> subdirectory, apart from 'unladen_swallow/perf.py' and adding some >> >> __init__.py somewhere. So at least these benchmarks did not receive >> >> any pypy-specific adapatations. If there are divergences, they come >> >> from changes done to the unladen-swallow benchmark suite after PyPy >> >> copied it on 2010-01-15. >> > >> > >> > I know that directory wasn't changed, but I also noticed that some >> > benchmarks had the same name, which is why I thought they were forked >> > versions of the same-named Unladen benchmarks. >> >> Not if they're in own/ directory. >> > > OK, good to know. I realized I can't copy code wholesale from PyPy's > benchmark suite as I don't know the code's history and thus if the > contributor signed Python's contributor agreement. Can the people who are > familiar with the code help move benchmarks over where the copyright isn't > in question? > > I can at least try to improve the Python 3 situation by doing things like > pulling in Vinay's py3k port of Django, etc. to fill in gaps. I will also > try to get the benchmarks to work with a Python 2.7 control and a Python 3 > "experimental" target for comparing performance since that's what I need > (or at least be able to run the benchmarks on their own and writing out the > results for later comparison). > > Anything else that should be worked on? > > _______________________________________________ > Speed mailing list > Speed(a)python.org > http://mail.python.org/mailman/listinfo/speed > > The important thing is that once a benchmark is in the repo it can *never* change including all the versions of dependencies, only Python can vary, otherwise you kill the ability to actually do science with the numbers. So, e.g., I wouldn't pull in Vijnay's fork, since that's going to be utterly obsolete in a few weeks probably, I'd wait to have django on py3k for that work to all be merged into django itself. 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

1 0

Re: [Speed] merging PyPy and Python benchmark suite
by Brett Cannon July 24, 2012

July 24, 2012

On Mon, Jul 23, 2012 at 7:34 PM, Maciej Fijalkowski <fijall(a)gmail.com>wrote: > On Mon, Jul 23, 2012 at 11:46 PM, Brett Cannon <brett(a)python.org> wrote: > > > > > > On Mon, Jul 23, 2012 at 4:39 PM, Armin Rigo <arigo(a)tunes.org> wrote: > >> > >> Hi Brett, > >> > >> On Mon, Jul 23, 2012 at 10:15 PM, Brett Cannon <brett(a)python.org> > wrote: > >> > That's what I'm trying to establish; how much have they diverged and > if > >> > I'm > >> > looking in the proper place. > >> > >> bm_mako.py is not from Unladen Swallow; that's why it is in > >> pypy/benchmarks/own/. In case of doubts, check it in the history of > >> Hg. The PyPy version was added from virhilo, which seems to be the > >> name of his author, on 2010-12-21, and was not changed at all since > >> then. > > > > > > 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. > > No we did not use those benchmarks. Those were mostly completely > artificial microbenchmarks (call, call_method etc.). We decided we're > not really that interested in microbenchmarks. > > > > >> > >> > >> Hg tells me that there was no change at all in the 'unladen_swallow' > >> subdirectory, apart from 'unladen_swallow/perf.py' and adding some > >> __init__.py somewhere. So at least these benchmarks did not receive > >> any pypy-specific adapatations. If there are divergences, they come > >> from changes done to the unladen-swallow benchmark suite after PyPy > >> copied it on 2010-01-15. > > > > > > I know that directory wasn't changed, but I also noticed that some > > benchmarks had the same name, which is why I thought they were forked > > versions of the same-named Unladen benchmarks. > > Not if they're in own/ directory. > OK, good to know. I realized I can't copy code wholesale from PyPy's benchmark suite as I don't know the code's history and thus if the contributor signed Python's contributor agreement. Can the people who are familiar with the code help move benchmarks over where the copyright isn't in question? I can at least try to improve the Python 3 situation by doing things like pulling in Vinay's py3k port of Django, etc. to fill in gaps. I will also try to get the benchmarks to work with a Python 2.7 control and a Python 3 "experimental" target for comparing performance since that's what I need (or at least be able to run the benchmarks on their own and writing out the results for later comparison). Anything else that should be worked on?

1 0

Re: [Speed] merging PyPy and Python benchmark suite
by Antoine Pitrou July 23, 2012

July 23, 2012

On Mon, 23 Jul 2012 17:46:29 -0400 Brett Cannon <brett(a)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

3 2