On Wed, Jul 25, 2012 at 3:18 PM, Maciej Fijalkowski <fij...@gmail.com>wrote:
> On Wed, Jul 25, 2012 at 8:16 PM, Brett Cannon <br...@python.org> wrote: > > > Great! Then I'm happy with moving PyPy benchmarks over wholesale. Are > there > > any benchmarks that are *really* good and are thus a priority to move, or > > any that are just flat-out bad and I shouldn't bother moviing? > > Note that not all benchmarks run nightly. twisted_accept for example > run out of TCP connections. benchmarks.py is your helper. We improved > the US runner qutie significantly (the main runner.py file), mostly by > improving reporting. So it can save a .json file or upload stuff to a > codespeed instance. > One thing at a time. =) > > Other than that, they all measure something. It's really up to you to > decide which ones measure "something significant". Of course for our > purposes benchmarks which require large libs are more interesting than > others, but they all do something interesting. We removed those that > we consider completely uninteresting. > I will start with ones that will port to Python 3 easily, then go from there.
_______________________________________________ Speed mailing list Speed@python.org http://mail.python.org/mailman/listinfo/speed
