Roundup Robot added the comment:
New changeset 428b6350307e by Benjamin Peterson in branch 'default':
add a pointer to the benchmarks repo (closes #17449)
http://hg.python.org/devguide/rev/428b6350307e
--
nosy: +python-dev
resolution: - fixed
stage: needs patch - resolved
status: open
Kavya Joshi added the comment:
I added a `Benchmarking` section in the dev guide with the relevant links and
the intended use (testing rather than optimizing).
I also added an entry for the section in the Index.
Testing/verification:
I built the docs and visually inspected them.
--
Antoine Pitrou added the comment:
Jeff: yes it could :) Do you want to provide a patch?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17449
___
Jeff Ramnani added the comment:
Now that bug #18586 is closed, could the Dev Guide point benchmarkers to the
benchmarks repo and its README?
http://hg.python.org/benchmarks/file/9a1136898539/README.txt
--
nosy: +jramnani
___
Python tracker
Ronald Oussoren added the comment:
Documenting this would be useful because it appears to be non-trivial to
actually run the benchmark suite with Python 3.
* Using python perf.py -b default fails due to some code in the
benchmarks that is not python3 compatible
* Using make_perf3.sh and
Antoine Pitrou added the comment:
* Using -b 2n3 instead instead of -b default or -b all works,
but
runs only a subset of the benchmark.
I think we should include a copy of the 2to3'ed third-party libs in
the benchmarks repo, this would running avoid the length and tedious
conversion on
Ronald Oussoren added the comment:
The overhead of 2to3 isn't too bad, especially because only a subset of the
benchmarks is translated in the first place.
It is more important that there is better documentation than there is now, it
seems that you're supposed to use either '-b 2n3' or
Antoine Pitrou added the comment:
The overhead of 2to3 isn't too bad, especially because only a subset
of the benchmarks is translated in the first place.
Well, the biggest time is spent translating the third-party libraries,
not benchmark files.
Also, it's simply tedious manual work (you
Ronald Oussoren added the comment:
The attached patch for the benchmark README.txt should document the status quo.
--
Added file: http://bugs.python.org/file31073/issue-18181-full-v3.txt
___
Python tracker rep...@bugs.python.org
Dave Malcolm added the comment:
On Mon, 2013-07-29 at 14:01 +, Ronald Oussoren wrote:
Ronald Oussoren added the comment:
The attached patch for the benchmark README.txt should document the status
quo.
--
Added file: http://bugs.python.org/file31073/issue-18181-full-v3.txt
Ronald Oussoren added the comment:
Sorry about that. I stored the patch file in the wrong directory and attached
the most recent file in the directory where I had expected the patch to be.
--
Added file: http://bugs.python.org/file31074/issue-17449-readme.txt
Changes by Ronald Oussoren ronaldousso...@mac.com:
Removed file: http://bugs.python.org/file31073/issue-18181-full-v3.txt
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17449
___
Brett Cannon added the comment:
I agree with Antoine that the time has come to drop make_perf3.sh and make it
so that Python 3 doesn't require a separate build of the benchmark directory.
Created http://bugs.python.org/issue18586 to track this idea.
--
Meador Inge added the comment:
I think this will be useful information. I tend to doing benchmarks
rather infrequently. Whenever I do them I forgot how I setup the suite
the previous time around.
In fact, I found this issue just now while googling for how to setup and
run the official
Changes by Edmond Burnett eburn...@gmail.com:
--
nosy: +edmond.burnett
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17449
___
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: - needs patch
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17449
___
Antoine Pitrou added the comment:
Mmmh... I'm not very warm on this one. If we start documenting the benchmark
suite in the devguide, then people will start to be all gung ho about it, be
obsessed with benchmark numbers, etc.
I guess what I'm saying is that *if* it's covered, then the very
Ezio Melotti added the comment:
Benchmarking is also useful to test that existing patches (that fix bug or add
features) don't have a negative effect on the performance. Some kind of
warning that advises against using benchmarks just to try and optimize
everything sounds like a good idea
Brett Cannon added the comment:
No it does not, but it should.
--
assignee: brett.cannon -
keywords: +easy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17449
___
New submission from Dave Malcolm:
Does the devguide document the benchmarking suite anywhere? I can't see it
anywhere in the index on http://docs.python.org/devguide/ and google doesn't
seem to show anything.
suggested content:
* how to run the benchmarks for a Python 2 implementation
*
20 matches
Mail list logo
