Hi Phyo, On 21 March 2017 at 05:53, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

Teating. Saw warning that it is much slower than pypy2? How much slower?

This warning should be removed or at least made much less strong. We didn't measure, but it passes many of the same tests for JIT-code quality now. Where did we leave such a warning? A bientôt, Armin.

I am so excited to jump to 3.5x , thanks a lot guys. Any significant difference compare to 2.7x or features not passing tests ? On Fri, Mar 24, 2017 at 12:25 AM Matti Picus <matti.picus@gmail.com> wrote:

On 23/03/17 12:46, Armin Rigo wrote:

...

Hi Phyo,

On 21 March 2017 at 05:53, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Teating. Saw warning that it is much slower than pypy2? How much slower? This warning should be removed or at least made much less strong. We didn't measure, but it passes many of the same tests for JIT-code quality now. Where did we leave such a warning?

A bientôt,

Armin. It's in the release notice/blog post. Sorry, a bit late to refine that now :( Matti

---

pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev

Hi Phyo, On 7 April 2017 at 11:09, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

I want to mean if there any Significant performance difference between Pypy 2.7x and 3.5x

You tell us. We don't have automatic benchmark runners for PyPy3.5. Our knowledge so far is limited to the test_pypy_c tests, which are not completely fixed but show that the JIT emits reasonable code at least in the common cases. A bientôt, Armin.

Hi Phyo, On 21 March 2017 at 05:53, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

Teating. Saw warning that it is much slower than pypy2? How much slower?

This warning should be removed or at least made much less strong. We didn't measure, but it passes many of the same tests for JIT-code quality now. Where did we leave such a warning? A bientôt, Armin.

I am so excited to jump to 3.5x , thanks a lot guys. Any significant difference compare to 2.7x or features not passing tests ? On Fri, Mar 24, 2017 at 12:25 AM Matti Picus <matti.picus@gmail.com> wrote:

On 23/03/17 12:46, Armin Rigo wrote:

...

Hi Phyo,

On 21 March 2017 at 05:53, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

...

Teating. Saw warning that it is much slower than pypy2? How much slower? This warning should be removed or at least made much less strong. We didn't measure, but it passes many of the same tests for JIT-code quality now. Where did we leave such a warning?

A bientôt,

Armin. It's in the release notice/blog post. Sorry, a bit late to refine that now :( Matti

---

pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev

Hi Phyo, On 7 April 2017 at 11:09, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:

I want to mean if there any Significant performance difference between Pypy 2.7x and 3.5x

You tell us. We don't have automatic benchmark runners for PyPy3.5. Our knowledge so far is limited to the test_pypy_c tests, which are not completely fixed but show that the JIT emits reasonable code at least in the common cases. A bientôt, Armin.