Re: [Speed] Status of speed.python.org?
Am 21.10.2012 11:08, schrieb Maciej Fijalkowski:
On Sat, Oct 20, 2012 at 1:21 PM, Carsten Senger <senger@rehfisch.de> wrote:
Am 19.10.2012 21:38, schrieb Miquel Torres:
Right. On the webapp (Codespeed) side of things I am willing to help in anything you need. The blocker has been mostly the benchmark runner, AFAIK.
Some month ago I worked on the benchmark runner and the build slave helpers in the pypy repository. They can run the test suite for both pypy and cpython. It will need no or minor tweeks to use python3. What was missing back then, and IIRC planned to be discussed at PyCo, was the port of the benchmarks to python 3.
Now it can be set up on speed.p.o (with minor adjustments if necessary). I'd do work on that too.
..Carsten
FYI the running on python 2 never worked (because of option passing). It roughly shows up how people care (or how much they know). I suppose we can declare "running benchmarks on python 2" a completely pointless exercise.
I know I cared. It worked with my patches that where merged by you. They removed the hard coded configuration from the build factories and the runner. I stopped then cause nobody was interested to collect data for 2.7 which would not receive notable changes. Same applied to historical data for python 2. Pointless describes that very well, but for different reasons.
There where no python 3 benchmarks and the how and when seemed more like a political discussion to me.
..Carsten
-- Carsten Senger - Schumannstr. 38 - 65193 Wiesbaden senger@rehfisch.de - (0611) 5324176 PGP: gpg --recv-keys --keyserver hkp://subkeys.pgp.net 0xE374C75A
On Sun, Oct 21, 2012 at 2:06 PM, Carsten Senger <senger@rehfisch.de> wrote:
Am 21.10.2012 11:08, schrieb Maciej Fijalkowski:
On Sat, Oct 20, 2012 at 1:21 PM, Carsten Senger <senger@rehfisch.de> wrote:
Am 19.10.2012 21:38, schrieb Miquel Torres:
Right. On the webapp (Codespeed) side of things I am willing to help in anything you need. The blocker has been mostly the benchmark runner, AFAIK.
Some month ago I worked on the benchmark runner and the build slave helpers in the pypy repository. They can run the test suite for both pypy and cpython. It will need no or minor tweeks to use python3. What was missing back then, and IIRC planned to be discussed at PyCo, was the port of the benchmarks to python 3.
Now it can be set up on speed.p.o (with minor adjustments if necessary). I'd do work on that too.
..Carsten
FYI the running on python 2 never worked (because of option passing). It roughly shows up how people care (or how much they know). I suppose we can declare "running benchmarks on python 2" a completely pointless exercise.
I know I cared. It worked with my patches that where merged by you. They removed the hard coded configuration from the build factories and the runner. I stopped then cause nobody was interested to collect data for 2.7 which would not receive notable changes. Same applied to historical data for python 2. Pointless describes that very well, but for different reasons.
There where no python 3 benchmarks and the how and when seemed more like a political discussion to me.
..Carsten
I'm sorry, my mail was definitely too harsh.
For what is worth, there are python 3 benchmarks now. Maybe we should somehow restart it?
Cheers, fijal
participants (2)
-
Carsten Senger -
Maciej Fijalkowski