This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | flox |
|---|---|
| Recipients | brett.cannon, docs@python, flox, jnoller, lemburg |
| Date | 2012年07月17日.13:50:24 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1342533025.73.0.137309811098.issue15369@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Actually, I discovered "python -m test.pystone" during the talk of Mike Müller at EuroPython. http://is.gd/fasterpy Even if they are suboptimal for true benchmarks, they should probably be mentioned somewhere. In the same paragraph, there should be a link to the "Grand Unified Python Benchmark Suite" as best practice: http://hg.python.org/benchmarks http://hg.python.org/benchmarks/file/tip http://hg.python.org/benchmarks/file/tip/README.txt The last paragraph of this wiki page might be reworded and included in the Python documentation: http://code.google.com/p/unladen-swallow/wiki/Benchmarks http://code.google.com/p/unladen-swallow/wiki/Benchmarks#Benchmarks_we_don't_use BTW, there's also this website which seems not updated anymore... http://speed.python.org/ |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年07月17日 13:50:25 | flox | set | recipients: + flox, lemburg, brett.cannon, jnoller, docs@python |
| 2012年07月17日 13:50:25 | flox | set | messageid: <1342533025.73.0.137309811098.issue15369@psf.upfronthosting.co.za> |
| 2012年07月17日 13:50:25 | flox | link | issue15369 messages |
| 2012年07月17日 13:50:24 | flox | create | |