Dan, What are the agreed upon constraints? A simple benchmark like pystone doesn't tell much. Large systems used for real work are more interesting and a more realistic measure of the language+implementation than small synthetic benchmarks. For example, Zope might be a good choice, but measuring its performance is an interesting (and difficult) problem in itself. On Sun, 14 Dec 2003, Dan Sugalski wrote: > Not to push, folks, but the python dev community was going to write > the benchmark program for the pie-off Guido and I are going to have > at OSCON 2004. We're supposed to have the bytecode for the program > frozen by the end of December 2003, a mere 16 days away. (I could > just go with pystone, I suppose, but even .NET's faster on that > one...) > -- > Dan > > --------------------------------------"it's like this"------------------- > Dan Sugalski even samurai > dan at sidhe.org have teddy bears and even > teddy bears get drunk > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/allison%40sumeru.stanford.edu >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4