On Sun, 30 Sep 2012 19:58:02 -0400 Brett Cannon <brett@python.org> wrote:
On Sun, Sep 30, 2012 at 7:21 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Hello,
The hexiom benchmark is very slow. Is there a reason it's included there?
Already been asked and answered: http://mail.python.org/pipermail/speed/2012-September/000209.html
I didn't realize when reading this discussion that hexiom2 was *that* slow. I don't think a benchmark taking 100+ seconds to run *in fast mode* has a place in the benchmark suite. PyPy can maintain their own benchmarks in their source tree, like CPython does.
Regards
Antoine.
-- Software development and contracting: http://pro.pitrou.net
On Mon, Oct 1, 2012 at 2:04 AM, Antoine Pitrou <solipsis@pitrou.net> wrote:
On Sun, 30 Sep 2012 19:58:02 -0400 Brett Cannon <brett@python.org> wrote:
On Sun, Sep 30, 2012 at 7:21 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
Hello,
The hexiom benchmark is very slow. Is there a reason it's included there?
Already been asked and answered: http://mail.python.org/pipermail/speed/2012-September/000209.html
I didn't realize when reading this discussion that hexiom2 was *that* slow. I don't think a benchmark taking 100+ seconds to run *in fast mode* has a place in the benchmark suite. PyPy can maintain their own benchmarks in their source tree, like CPython does.
Regards
Antoine.
I strongly disagree. There are quite a few slow benchmarks that are very useful, like pypy translation toolchain. How about you skip this one in fast mode?
participants (2)
-
Antoine Pitrou -
Maciej Fijalkowski