On Mon, Feb 8, 2016 at 1:09 PM, Yury Selivanov wrote:
> Zachary,
>
> Do you run the benchmarks in rigorous mode?
Not currently. I think I need to reschedule when the benchmarks are
run anyway, to avoid conflicts with PyPy's usage of that box, and will
add rigorous mode when I do that.
--
Zach
Zachary,
Do you run the benchmarks in rigorous mode?
Yury
On 2016-02-04 1:48 AM, Zachary Ware wrote:
I'm happy to announce that speed.python.org is finally functional!
There's not much there yet, as each benchmark builder has only sent
one result so far (and one of those involved a bit of chea
To piggyback on Zach's speed.python.org announcement, we will most likely
be kicking off a discussion of redoing the benchmark suite, tweaking the
test runner, etc. over on the speed@ ML. Those of us who have been doing
perf work lately have found some shortcoming we would like to fix in our
benchm
Big thanks to you, Zachary (and everyone involved)! It's a very good news.
Yury
On 2016-02-04 1:48 AM, Zachary Ware wrote:
I'm happy to announce that speed.python.org is finally functional!
There's not much there yet, as each benchmark builder has only sent
one result so far (and one of those
On 4 February 2016 at 16:48, Zachary Ware wrote:
> I'm happy to announce that speed.python.org is finally functional!
> There's not much there yet, as each benchmark builder has only sent
> one result so far (and one of those involved a bit of cheating on my
> part), but it's there.
>
> There are
On 4 February 2016 at 16:48, Zachary Ware wrote:
> I'm happy to announce that speed.python.org is finally functional!
> There's not much there yet, as each benchmark builder has only sent
> one result so far (and one of those involved a bit of cheating on my
> part), but it's there.
>
> There are
Great!
2016-02-04 7:48 GMT+01:00 Zachary Ware :
> I'm happy to announce that speed.python.org is finally functional!
> There's not much there yet, as each benchmark builder has only sent
> one result so far (and one of those involved a bit of cheating on my
> part), but it's there.
>
> There are l
I'm happy to announce that speed.python.org is finally functional!
There's not much there yet, as each benchmark builder has only sent
one result so far (and one of those involved a bit of cheating on my
part), but it's there.
There are likely to be rough edges that still need smoothing out.
When
> On Jun 22, 2015, at 6:58 PM, Zachary Ware
> wrote:
>
> On Thu, Jun 4, 2015 at 10:51 AM, Maciej Fijalkowski wrote:
>> On Thu, Jun 4, 2015 at 4:32 PM, R. David Murray
>> wrote:
>>> OK, so what you are saying is that speed.python.org will run a buildbot
>>> slave so that when a change is commi
On 23.06.2015 03:58, Zachary Ware wrote:
> On Thu, Jun 4, 2015 at 10:51 AM, Maciej Fijalkowski wrote:
>> On Thu, Jun 4, 2015 at 4:32 PM, R. David Murray
>> wrote:
>>> OK, so what you are saying is that speed.python.org will run a buildbot
>>> slave so that when a change is committed to cPython,
On Thu, Jun 4, 2015 at 10:51 AM, Maciej Fijalkowski wrote:
> On Thu, Jun 4, 2015 at 4:32 PM, R. David Murray wrote:
>> OK, so what you are saying is that speed.python.org will run a buildbot
>> slave so that when a change is committed to cPython, a speed run will be
>> triggered? Is "the runner"
On Thu, Jun 4, 2015 at 4:32 PM, R. David Murray wrote:
> On Thu, 04 Jun 2015 12:55:55 +0200, "M.-A. Lemburg" wrote:
>> On 04.06.2015 04:08, Tetsuya Morimoto wrote:
>> >> If someone were to volunteer to set up and run speed.python.org, I think
>> > we could add some additional focus on performance
On Thu, 04 Jun 2015 12:55:55 +0200, "M.-A. Lemburg" wrote:
> On 04.06.2015 04:08, Tetsuya Morimoto wrote:
> >> If someone were to volunteer to set up and run speed.python.org, I think
> > we could add some additional focus on performance regressions. Right now,
> > we don't have any way of reliabl
On 04.06.2015 04:08, Tetsuya Morimoto wrote:
>> If someone were to volunteer to set up and run speed.python.org, I think
> we could add some additional focus on performance regressions. Right now,
> we don't have any way of reliably and reproducibly testing Python
> performance.
>
> I'm very inter
Now that we have the machine, we need to start working on
collecting/organizing the resources needed to get a shared codespeed
system in place. After speaking with various people, we felt that
overloading codespeed-dev, pypy-dev or python-dev with the discussions
around this would be sub optimal. I
On Wed, Jun 29, 2011 at 10:05 PM, Jesse Noller wrote:
> I've posted a more expansive entry on my blog:
> http://jessenoller.com/2011/06/29/announcing-the-new-speed-python-org-machine/
>
> But the short version, that as discussed at the VM and language
> summit, we now have a hosted machine dedicat
I've posted a more expansive entry on my blog:
http://jessenoller.com/2011/06/29/announcing-the-new-speed-python-org-machine/
But the short version, that as discussed at the VM and language
summit, we now have a hosted machine dedicated to the running of
cross-interpreter speed tests, etc. The har
17 matches
Mail list logo
