just saw: speed.pypy.org reports 4x faster
I recommend to wrap the code and release it with the subtitle "the 4 times faster release" Best wishes, Harald -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 Amtsgericht Stuttgart, HRB 734971 - persuadere. et programmare
On Mon, Jul 18, 2011 at 11:30 PM, Massa, Harald Armin <chef@ghum.de> wrote:
I recommend to wrap the code and release it with the subtitle "the 4 times faster release"
I like codenames more. Like PyPy 1.6 "Kickass Panda"
Best wishes, Harald -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607
Amtsgericht Stuttgart, HRB 734971 - persuadere. et programmare
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
So This is really happening in 1.6 or Speed.pypy bug? On 7/19/11, Maciej Fijalkowski <fijall@gmail.com> wrote:
On Mon, Jul 18, 2011 at 11:30 PM, Massa, Harald Armin <chef@ghum.de> wrote:
I recommend to wrap the code and release it with the subtitle "the 4 times faster release"
I like codenames more. Like PyPy 1.6 "Kickass Panda"
Best wishes, Harald -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607
Amtsgericht Stuttgart, HRB 734971 - persuadere. et programmare
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
@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-repr) or a benchmarking anomaly? Miquel 2011/7/18 Phyo Arkar <phyo.arkarlwin@gmail.com>:
So This is really happening in 1.6 or Speed.pypy bug?
On 7/19/11, Maciej Fijalkowski <fijall@gmail.com> wrote:
On Mon, Jul 18, 2011 at 11:30 PM, Massa, Harald Armin <chef@ghum.de> wrote:
I recommend to wrap the code and release it with the subtitle "the 4 times faster release"
I like codenames more. Like PyPy 1.6 "Kickass Panda"
Best wishes, Harald -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607
Amtsgericht Stuttgart, HRB 734971 - persuadere. et programmare
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
_______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Massa, Harald Armin, 18.07.2011 23:30:
I recommend to wrap the code and release it with the subtitle "the 4 times faster release"
Just nitpicking here, but you shouldn't forget that any given set of benchmarks can only ever be an arbitrary one. If you change the current set, you can rightfully make any claim from "PyPy is 100x faster than CPython on average" to "CPython is substantially faster than PyPy". Taking the average is a nice addition right below the graphs on speed.pypy.org, but makes no sense at all without this context. Stefan
On Thu, Jul 21, 2011 at 7:17 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
Massa, Harald Armin, 18.07.2011 23:30:
I recommend to wrap the code and release it with the subtitle "the 4 times faster release"
Just nitpicking here, but you shouldn't forget that any given set of benchmarks can only ever be an arbitrary one. If you change the current set, you can rightfully make any claim from "PyPy is 100x faster than CPython on average" to "CPython is substantially faster than PyPy". Taking the average is a nice addition right below the graphs on speed.pypy.org, but makes no sense at all without this context.
Of course :) No single number would ever describe the speed of something as complex as a python interpreter (unless the number is 42 of course). However, there were request to reduce it to that and here we have one. I don't think "4x faster now!" is a good marketing slogan even. What's significant however is that it's getting faster with each release. Cheers, fijal
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 <fijall@gmail.com>:
On Thu, Jul 21, 2011 at 7:17 AM, Stefan Behnel <stefan_ml@behnel.de> wrote:
Massa, Harald Armin, 18.07.2011 23:30:
I recommend to wrap the code and release it with the subtitle "the 4 times faster release"
Just nitpicking here, but you shouldn't forget that any given set of benchmarks can only ever be an arbitrary one. If you change the current set, you can rightfully make any claim from "PyPy is 100x faster than CPython on average" to "CPython is substantially faster than PyPy". Taking the average is a nice addition right below the graphs on speed.pypy.org, but makes no sense at all without this context.
Of course :)
No single number would ever describe the speed of something as complex as a python interpreter (unless the number is 42 of course). However, there were request to reduce it to that and here we have one. I don't think "4x faster now!" is a good marketing slogan even. What's significant however is that it's getting faster with each release.
Cheers, fijal _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
participants (5)
-
Maciej Fijalkowski -
Massa, Harald Armin -
Miquel Torres -
Phyo Arkar -
Stefan Behnel