Hi Matti,
I'll gladly help setting up the speed site
El El mié, 31 ene 2018 a las 13:47, Victor Stinner
escribió:
> Hi,
>
> I tried but failed to find someone in PyPy to adjust performance
> benchmarks for PyPy. Currently, the JIT is not properly warmed up, and
> the results can be dishonnest o
> >
> >> > http://mail.python.org/pipermail/speed/2012-October/000224.html
> >> >
> >> > There is even an (empty) instance running setup by Miquel Torres (the
> >> > author of codespeed, the software behind speed.pypy.org) at:
> >> >
> >>
Thanks Davide. It's fixed now.
Cheers
Miquel
2011/11/4 Davide Setti :
> Hi,
>
> If i click on the permalink link on
>
> http://speed.pypy.org/timeline/#/?exe=3,6,1,5&base=2+472&ben=grid&env=1&revs=200&equid=off
>
> i get:
>
> http://speed.pypy.org/timeline/?exe=3%2C6%2C1%2C5&base=2%2B472&ben=gri
Done, I tagged revision 46161:eb30a0ef328e (1st of August) as PyPy
1.6. Can be seen now on the start page.
Cheers,
Miquel
2011/9/8 Antonio Cuni :
> On 08/09/11 12:15, Miquel Torres wrote:
>>
>> which sadly doesn't have data on speed.pypy.org (not all data saved on
>> t
which sadly doesn't have data on speed.pypy.org (not all data saved on
the removed environment was kept, sorry). The August 1st revision is
probably not acceptable to portrait as being 1.6 ...
2011/9/8 Antonio Cuni :
> On 08/09/11 10:46, Maciej Fijalkowski wrote:
>
>>> What about starting the ben
Which revision is (or "simulates") 1.6?
2011/9/3 Alex Gaynor :
> Can someone with the appropriate permissions add a tag for 1.6 on
> speed.pypy.org?
> Thanks,
> Alex
>
> --
> "I disapprove of what you say, but I will defend to the death your right to
> say it." -- Evelyn Beatrice Hall (summarizin
You can also do that in Github, which I prefer.
However, since CPython and PyPy use mercurial, the general preference
for Bitbucket is understandable.
2011/9/1 Brett Cannon :
> On Thu, Sep 1, 2011 at 01:10, Nick Coghlan wrote:
>> On Thu, Sep 1, 2011 at 5:50 PM, Antonio Cuni wrote:
>>> On 31/08
n Aug 31, 2011, at 11:34 AM, Miquel Torres wrote:
>
>> Hi all,
>>
>> though I took up on the task of installing a Codespeed instance
>> myself, I didn't have time until now. This weekend I will definitely
>> have a *lot* of time to work on this, so count on that t
Hi all,
though I took up on the task of installing a Codespeed instance
myself, I didn't have time until now. This weekend I will definitely
have a *lot* of time to work on this, so count on that task being
done by then.
The bitbucket issue tracker is a start (though a organization account
would
so the situation is even better: even if the PyPy Python 2.x
implementation was not updated any more after 1.6 (which won't be the
case), future versions of PyPy could have *both* a 2.x and a 3.x
interpreter (separately packaged), and *both* would leverage the newer
JIT versions. Is that correct Ma
@Armin
> This would remain as a branch for the foreseeable future though,
> because we still need a Python 2 interpreter, if only to run our own
> translation toolchain on (and not suffer the 2.5x slow-down of running
> it on CPython 2.x).
I don't quite follow. Switching to Python 3 (I am not sayin
ly see a list
of executables. Improving that is a theme for the GSoC
I will be able to work on this next week, so I maybe we can meet on
IRC and have a go at it? (and close this huge email thread ;-)
2011/7/28 Antonio Cuni :
> Hi Miquel,
>
> On 28/07/11 11:04, Miquel Torres wrote:
>&
tables
into two different projects. pypy32, pypy64, instead of different
environements. The revision list shown does change on-the-fly
depending on the project the selected exe belongs to.
Cheers,
Miquel
2011/7/27 Antonio Cuni :
> Hi Miquel,
>
> On 25/07/11 21:09, Miquel Torres wrote:
>
Very nice!
2011/7/26 Antonio Cuni :
> On 25/07/11 21:09, Miquel Torres wrote:
>>
>> Btw., in any case you can start saving results in separated
>> environments. That will at least make changes work right away, and it
>> does make sense to have "tannit 32 bits"
Btw., in any case you can start saving results in separated
environments. That will at least make changes work right away, and it
does make sense to have "tannit 32 bits" and "tannit 64 bits".
Miquel
2011/7/21 Miquel Torres :
> Ok, not much time right now, but we will loo
Ok, not much time right now, but we will look into it.
2011/7/21 Maciej Fijalkowski :
> On Thu, Jul 21, 2011 at 1:52 PM, Antonio Cuni wrote:
>> On 21/07/11 10:02, Miquel Torres wrote:
>>> Alternatively, the timeline view could allow to display several
>>> en
Alternatively, the timeline view could allow to display several
environments at the same time...
2011/7/21 Antonio Cuni :
> On 21/07/11 09:13, Maciej Fijalkowski wrote:
>> I think having them at the same graph is more important than having
>> changes showing correct things. I might give it a go i
Right. I think that the geometric average is useful mostly and
primarily to gather how PyPy is improving over time, and much less to
know whether it has yet reached the speed of light as compared to
CPython ;-)
2011/7/21 Maciej Fijalkowski :
> On Thu, Jul 21, 2011 at 7:17 AM, Stefan Behnel wrot
force buildbot to update to a more specific
>revision. E.g., "the highest revision of today at 00:00", or something like
>this. This should ensure to have the same revision for all our
>benchmarks/tests.
Sounds good to me.
Miquel
2011/7/20 Maciej Fijalkowski :
> On Wed, Jul
sorry, I have currently two busy days and couldn't look yet at it.
Will do as soon as I can
2011/7/19 Antonio Cuni :
> On 18/07/11 22:36, Miquel Torres wrote:
>> Ok, it is fixed now.
>>
>> AND branch support is in. Results saved with branch other than
>> &q
@Phyo: it's because revision 45700 shows a large improvement for telco
and spitfire_stringio (40%+), which makes for an average improvement
of over 6%. See detailed changes table:
http://speed.pypy.org/changes/?tre=10&rev=45700%3Ac3294f3c5888&exe=1&env=1
Due to Maciej's commit (merge numpy-str-rep
Ok, it is fixed now.
AND branch support is in. Results saved with branch other than
"default" will be available in the comparison view. Got to talk to
fijal yet to see how we should benchmark branches...
Ciao!
Miquel
2011/7/18 Antonio Cuni :
> On 18/07/11 21:37, Miquel Torres
g. If that can be done, we can upgrade the current
setup in no time.
2011/7/12 holger krekel :
> On Tue, Jul 12, 2011 at 09:19 +0200, Maciej Fijalkowski wrote:
>> On Tue, Jul 12, 2011 at 9:16 AM, Miquel Torres wrote:
>> > Branches are already implemented. speed.pypy.org just ne
Branches are already implemented. speed.pypy.org just needs to be
upgraded to Codespeed 0.8.x and its data migrated.
That has not yet been done because we wanted to move to ep.io, which
has not yet happend, and we are working on speed.python.org and
somehow things have stalled.
Migrating current
I have answered on the Codespeed discussion group.
Maciej is right that you should actually run bechmarks on a separate,
clean box, which then posts results to the Codespeed instance.
Miquel
2011/6/16 Maciej Fijalkowski :
> On Thu, Jun 16, 2011 at 4:32 AM, Chuck Remes wrote:
>> I'm working on
25 matches
Mail list logo
