On Sat, Apr 4, 2009 at 9:01 PM, Raymond Hettinger <python@rcn.com> wrote:
Instead of benchmarking the kind of things we prefer to do in C,
CPython prefers to do some things in C because it can and doing so is faster. The other implementations can't, and I think it's a fair comparison to show the penalty that incurs. For that matter, it's useful to show how much of a win CPython gets from the extra complexity of the C extension module. If that win gets too small, it'd be nice to delete the C extension. The implication of this is that the benchmark should be able to run either the C or pure-Python implementation, independently for the two pythons being compared. The Unladen Swallow benchmarks currently aren't very good at that and should be extended. On the other hand, we already have the pickling tests, which can show some of the C/non-C difference.
how about something like timing the sphinx build for the rst docs? This is something that represents a real and typical use of Python.
Also a good benchmark.
----- Original Message ----- From: "Antoine Pitrou" <solipsis@pitrou.net> To: "Michael Foord" <michael@voidspace.org.uk> Cc: "Collin Winter" <collinw@gmail.com>; "Michael Foord" <fuzzyman@voidspace.org.uk>; "stdlib-sig" <stdlib-sig@python.org> Sent: Saturday, April 04, 2009 5:52 PM Subject: [stdlib-sig] Benchmark suggestion
hi,
A possible benchmark addition could be json parsing/unparsing using the pure Python parts of the simplejson library.
Other things which would be interesting to measure: - a production-grade HTTP implementation (some parts of Twisted? something else?) - something involving Unicode
cheers
Antoine.
_______________________________________________ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
_______________________________________________ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
-- Namasté, Jeffrey Yasskin http://jeffrey.yasskin.info/